I think I might have a solution to your problem, I was working with one of the monday team a few months ago and I think you could edit it to suit your needs.
- Create your own custom action of “create update an item with mapping and add an update”, in this action you’ll use monday’s Item mapping field type and board field type as input fields.
- Create your own custom trigger of “when an entity is created/updated” like you’ve done so far
- Now while calling your action you’ll get as an object the new monday item after the mapping, with it you could create an item
- when first creating the item you’ll get the newly created item id (after running the mutation at your server), save this item id as you will need it to create the update
- Once you have created the item, you can run a mutation to create the update using the ID returned from the create_item mutation
In order for this to work, I think you could get the update value a few different ways. You could either store it in your DB and then retrieve it with an ID from the mapped fields, or you could include it as a value in the mapped fields as Dipro suggested.
When your action is called with the mapped fields, you would then remove the update value from the mapped fields (you might need a text column on the board to ensure that the update is mapped and passed to your action), create the item, and then use the mapped value for the update to create the update
Let me know if you need more information to get this to work for you.