What is your goal?
I have a Notion database with a multi-select property called “Option”.
When I select one or more values in this field for a given item, I want it to automatically trigger the creation of an option in Orféo via its API.
But beyond just creating the option, I also want to send the full data from the Notion row to Orféo at the same time.
What I’m trying to achieve:
Watch for updates in a Notion database item
Detect when the “Option” multi-select field contains one or more values
Retrieve the data from that Notion row
Send this data to Orféo via API (HTTP module) to create the option
Avoid duplicates if the option or record already exists in Orféo
What is the problem?
Main questions:
What would be the most reliable Notion trigger in Make for this use case? (Watch Database Items vs Watch Page Updates, etc.)
Is using a multi-select field as a trigger condition reliable, or would you recommend a different approach?
For handling multiple selected values, would you use an iterator and create one API call per option?
What’s the best way to map and transform Notion data before sending it to a custom API?
How would you handle deduplication properly?
Store an Orféo ID back in Notion?
Or check existence first via API before creating?
Has anyone here already connected Orféo to Make via HTTP module or worked with a similar custom API integration?
What have you tried so far?
Notion (Watch updates) → filter if “Option” is not empty → retrieve properties → iterator (if needed) → HTTP request to Orféo API → store returned ID in Notion.
I’m mainly looking for best practices regarding structure, reliability, and avoiding edge cases.
Any feedback or example scenarios would be greatly appreciated.