Integrations: Native Recipes, API, and Webhooks
What this domain tests
Integrations questions check whether you know the difference between a native recipe, an automation, and an API/webhook connection, plus how data maps between monday.com and another tool.
Core rules and concepts
- The Integrations area of the automation center offers prebuilt recipes with a trigger in one tool and an action in another, such as Slack, Gmail, Google Calendar, Outlook, Teams, GitHub, Jira, Salesforce, HubSpot, Typeform, Zapier, and Make.
- Most native recipes are one-way; some calendar and CRM syncs are bidirectional. Confirm direction before promising a sync.
- Zapier/Make connect through monday.com's API; webhooks send an HTTP POST when an event occurs. The public API is GraphQL at
https://api.monday.com/v2and authenticates with an API token. - Integrations are configured per board or account, and some are gated by plan or admin approval.
Worked example
A Typeform submission should create an item and alert a Slack channel. Use the Typeform recipe: trigger = new entry; action 1 = create item in the Requests board; map the form fields to columns; action 2 = post to Slack. Reasoning: the trigger is external, the board action writes data, and the Slack action notifies; no automation is needed unless you add conditions.
Traps
Calling a connect boards column an integration; assuming every recipe syncs both ways; pointing a webhook at a private URL; exposing API tokens in shared docs; and forgetting that field mapping must match column types.