SupportSyndicate + Make (Integromat)
Visual automation workflows for SupportSyndicate — triggers, filters, and multi-step scenarios without code.
SupportSyndicate's Make integration provides the same core trigger and action set as the Zapier integration — new tickets, resolved conversations, escalations, lead captures — through Make's visual scenario builder. Make's advanced routing, iteration, and data transformation capabilities make it the preferred choice for teams that need complex multi-step workflows, conditional branching, or integration with apps not available on Zapier.
What data flows between the two systems
Every event, record, and update that passes between SupportSyndicate and Make (Integromat).
Fires when a conversation is created, with customer email, channel, subject, and first message as the payload.
Fires on ticket close with resolution type, CSAT score, handle time, and agent name.
Fires when the AI escalates to a human, with confidence score, sentiment, and escalation reason.
Fires when a visitor submits a lead form, with name, email, company, and any custom fields.
Allows Make scenarios to inject tickets into SupportSyndicate from external systems.
How to set up the Make (Integromat) integration
Most teams are live in under 15 minutes. No developer required.
Generate a Make API key
In SupportSyndicate Dashboard → Settings → API Keys, create a key with Make scope. Copy the key.
Add SupportSyndicate module in Make
In Make, search for SupportSyndicate in the module list, click Add a Connection, and paste your API key.
Build your scenario
Add a SupportSyndicate trigger module (e.g., Watch New Tickets), connect it to your target app module, and map the fields. Add filters, routers, and transformers as needed.
Test and schedule
Run the scenario manually with a test ticket to verify field mapping, then set the schedule (every 15 minutes is the Make default; instant triggers are supported on paid Make plans).
What teams use this integration for
Multi-step CRM enrichment
When a ticket resolves, update the CRM contact record, log the ticket in a spreadsheet, send a Slack notification, and trigger a Klaviyo flow — all in one Make scenario.
Conditional routing by channel
Route WhatsApp escalations to a different Slack channel than email escalations using Make's router module and channel-field filter.
Airtable reporting dashboard
Sync all closed tickets to Airtable with resolution type, CSAT, and handle time for custom reporting beyond SupportSyndicate's built-in analytics.
Google Sheets daily digest
Append a row to a Google Sheet every time a ticket resolves, enabling the team to build custom pivot-table reports.
Frequently asked questions
What is the difference between the Zapier and Make integrations?
Both cover the same SupportSyndicate trigger and action events. Make is better for complex multi-step scenarios with conditional branching, data transformation, and array iteration. Zapier is faster to set up for simple one-step automations. Many teams use Zapier for simple workflows and Make for complex ones.
Does Make support real-time (instant) triggers from SupportSyndicate?
Yes — on Make paid plans (Core and above), instant triggers via webhook deliver events in real time. Make Free and Basic use polling, which checks for new events every 15 minutes.
Is the Make integration available on all SupportSyndicate plans?
API key generation for Make and Zapier is available on all paid SupportSyndicate plans. The free tier does not include API access.