monday.com's integration center ships one-click connectors to Slack, Microsoft Teams, Gmail, Outlook, Salesforce, Mailchimp, GitHub, and a growing app marketplace, plus generic webhook support for anything not already listed. Each one works well for a single trigger and a single standard action. We build what happens when your real process needs more than one field, more than one condition, or a system monday.com's marketplace never got around to listing.
The integration center is recipe-based, the same way monday.com's internal automations are: pick a trigger from one app, pick an action in another, and it runs on standard fields. The Slack connector posts a message when a status changes. The Salesforce connector can create or update a lead when an item moves. The Gmail and Outlook connectors turn an incoming email into a board item. QuickBooks, HubSpot, and Mailchimp connectors exist too, though they cover a narrower set of triggers than the bigger-name integrations do.
Webhooks fill the gap for anything not on the list: monday.com can call out to a URL when something happens on a board, and can receive an inbound webhook to create or update an item. That's the same mechanism we use when we build a custom connection monday.com's marketplace doesn't ship natively.
If you're after the full GraphQL API that powers all of this, including authentication, rate limits, and what's left to the apps framework, we cover that in more depth on our monday CRM API page rather than repeating it here.
The native Salesforce connector moves standard fields on standard triggers. We map your custom fields both directions, so a board item and a Salesforce record stay in sync on the logic your sales process actually uses.
monday.com's QuickBooks connector covers a narrow set of actions. When an invoice needs to carry line items, terms, and a customer match pulled straight from the board, we build that directly against both APIs instead of working around the connector's limits.
If the native connector got you 70% of the way there and stalled on custom fields or a trigger it couldn't see, that's exactly the kind of gap we close.
Tell us which system you're trying to connect it to and which part of the native connector falls short, a missing field, a trigger it can't see, a system it never listed at all. We'll scope what closing that gap actually takes. monday.com is today's example; n-frames builds this same layer for whatever tool your business runs.
Let's talk →There's a native QuickBooks connector in the integration center, but it covers a limited set of triggers and actions compared to monday.com's bigger integrations like Slack or Salesforce. For anything beyond that, a custom connection built against both APIs usually gets you the rest of the way.
Yes, there's a native HubSpot connector in the app marketplace, covering common triggers like a deal stage changing or a new contact being created. Teams running more custom HubSpot properties or pipeline logic than the connector maps often end up building the rest themselves.
Yes, this is one of monday.com's most-used integrations: pick a trigger (status changes, a new item is created, a date arrives) and a Slack channel or person, and it fires automatically. It covers the simple notification case well.
Yes, both directions. monday.com can call out to an external URL when something happens on a board, and it can receive an inbound webhook to create or update items. Webhooks are the mechanism behind most of the custom integrations we build when a native connector doesn't exist.
Automations handle logic entirely inside monday.com, a status change updating another column on the same board. The integration center is specifically for connecting to outside apps, Slack, Salesforce, Gmail, and the rest. Functionally they're built the same way, trigger and action, just aimed at different targets.