Dynamic mapping entity to monday from built-in trigger

Hello there @egon and welcome to the community!

If I understand correctly, what you want, is that whenever an item is created in a monday board, it triggers an integration recipe that fetches data from your end, and uses that data to populate column values for that item in the board. Correct?

How would your endpoint know which entity from your end to use? Would the new item be created with an already populated column value such as “Entity ID” that you would then compare on your end with your data?

Looking forward to hearing from you!

Cheers,
Matias

Hello @Matias.Monday,

That is indeed what i am trying to achieve.
The name of the newly created item will be a reference to the entity on my side (Entity ID) that will be passed to the endpoint.

If I am correct i could achieve this with a custom action for every column i want to populate. The user could then define the property of the entity it wants to get (from a list field type f.e.) and the target column in monday where this information should be populated.
This workflow is very similar to the quickstart integration example from Monday.com.

Only it seems like this could blow up into adding a lot of actions to the automation for every column they want to populate.

The dynamic mapping feature seams like it would be able to show the user all possible properties it can receive for that entity and let the user select which columns to populate, all in 1 configuration.
But i only see a possibility to use this feature with subscribing and webhooks, and not with an ‘item created’ trigger coming from Monday.com.

Thanks in advance for your assistance!

Hello there @egon,

I heard back from our team. To achieve this functionality with the current recipe template builder, you’ll need to implement a custom trigger to enrich the data from the third-party system after the item has been created.

Here’s the recommended approach:

1. Create a custom dynamic mapping field

   • The field’s endpoint should return the fields from the third-party system.

2. Add a custom trigger

   • This trigger will retrieve and produce the enriched data from the third-party system.

3. Use an item_created webhook

   • This step ensures the custom trigger knows when to execute and perform the enrichment after an item is created. When the endpoint of your webhook is called, you can then trigger your custom trigger.