Integrations
The apps you can connect, what a connection is, and how connector operations reach them from actions and automations.
Snoze connects to other systems in three different ways. Picking the right one is most of the work.
| Way in | Use it for |
|---|---|
| Connector operation | A typed operation on a connected app — post to Slack, create a Jira issue |
| Data source | Pulling an external table in so it behaves like workspace data. See Connect external data |
| HTTP request | Anything without a connector — any URL, any method |
Connectable apps
Airtable, Discord, GitHub, Google Workspace, HubSpot, Intercom, Jira, Linear, Microsoft 365, Notion, Salesforce, Shopify, Slack, Stripe, Twilio, and Zendesk.
Connections
A connection is one authorised link to one account of one provider — your workspace’s Slack, a specific GitHub org. Create connections in workspace settings; authorise once, reuse everywhere.
Because a connection is a workspace object, an action or automation references the connection, not credentials. Rotating access is done in one place and nothing else changes.
Using one
From an action — create a Connector operation action, pick the connector, the operation, and the connection. Now any button or automation can run it. See Actions.
From an automation — add a Connector operation node directly, and feed its inputs from earlier steps with expressions. See Automations.
From an HTTP request action — for endpoints with no connector, an HTTP request action can still reference a connection so it borrows that authorisation instead of you pasting a token into a header.
Sending data out
- Outbound webhooks — Snoze POSTs to your URL when things happen
- HTTP request actions — Snoze calls you, on demand or from an automation
- Inbound webhooks — an external system POSTs into a webhook-triggered automation
All three are covered in Automate with webhooks.
Bringing data in
- Data sources sync an external table into the workspace so views, dashboards and automations treat it like any other data.
- The Refresh data source action re-pulls one on demand — bind it to a button, or run it on a schedule from an automation.
For developers
Building against Snoze itself — the API, the MCP server, API keys and scopes — is covered in Set up the MCP server, API keys and scopes, and the developer docs.