Integrations directory
Where every integration lives, the three ways they connect, what pausing does that disconnecting does not, and who is allowed to authorise an account.
Every integration in Zyan lives in one place: SettingsIntegrations. It is a searchable grid of tiles grouped into twelve categories, and each tile opens a connect card with a status pill and an on/off switch. If you cannot find where a provider is configured, it is here.
Before you start
Most connections are owner or admin only — non-owners see A workspace owner or admin can authorize and disconnect accounts. Some personal Pipedream accounts can be connected by an entitled member.
The twelve categories
The grid is grouped into twelve categories:
- Content & publishing
- Communication
- Email marketing
- Scheduling
- CRM & data
- Projects & tasks
- Lead capture
- Advertising
- Payments & bookkeeping
- Analytics & SEO
- Prospecting & outreach
- Automation & developer
Search rather than scan — the search box is faster than deciding which category a provider was filed under. With nothing matching you get No integrations match.
Three ways a provider connects
| Method | What happens | Examples |
|---|---|---|
| OAuth | You sign in at the provider and grant scopes | Google Ads, Slack, Gmail, Google Sheets, Google Calendar, Make, Zapier |
| Pasted key | You paste an API key or token, verified live before it is stored | Twilio, Telnyx, Adsterra, Resend (your own account), Apollo, People Data Labs, ScraperAPI, Supabase, Vercel |
| Pipedream sign-in | Pipedream manages the provider OAuth; Zyan stores only a binding | Notion, Airtable, Outlook, HubSpot, Teams, LinkedIn, Pipedrive, Mailchimp, Constant Contact, Attio, Zoho CRM, Salesforce, Asana, ClickUp, Klaviyo, HighLevel, Google Business Profile, Google Forms, Calendly, Acuity Scheduling, Typeform, Webflow, Tally, Fillout, DocuSign, PandaDoc, Zoom, Microsoft Calendar, OneDrive, Linear, Jira, Fathom, Grain, Dropbox, Box, Dropbox Sign, Canva |
Webhooks is the fourth case, and the odd one out: it needs no provider account at all.
Pipedream-backed connections
These carry the note Sign-in by Pipedream on the card.
Open the provider's tile and click Connect
The card notes Sign-in by Pipedream — Pipedream manages the sign-in.
Complete the provider's sign-in and grant scopes
At the provider, not in Zyan.
Select the resources the actions may write to
The page, base, list, project or location. This is the part people skip.
Use the provider's step in an automation
The Inspector offers the resources you selected.
Zyan stores only a binding — never the provider's tokens.
Connecting is not the same as being able to write
Selecting an account does not prove write access. The resources you picked and what the provider actually allows remain provider-gated. Test the step on a real record before you build a process on it.
Reconnecting needs the same person
A reconnect requires the original consenting actor and a verified provider identity, so an account cannot be silently swapped underneath a running automation. If the colleague who connected it has left, reconnect as a new connection rather than trying to inherit theirs.
Pipedream-backed connections are not available in client-scoped workflows or in the iOS admin shell.
Where the newer connections show up
| Connection | Where it shows up |
|---|---|
| Asana, ClickUp, Linear, Jira | A Work task links to a provider task or issue and shows its status; a create step links the task it creates to the run's Work task |
| Fathom, Grain | Meeting notes on the account row: each recorded meeting can start an automation, and a matched client gets an internal note |
| OneDrive, Dropbox, Box | Files → import selected files as copies; they follow the folder's permissions and stay after you disconnect |
| Dropbox Sign | Link signature requests to a lead or deal; a completed request starts the e-signature trigger (checked every few hours, or on Refresh) |
| Canva | Content Center → Library → Import assets: a chosen design comes in as images, one per page, up to five pages |
Make and Zapier
Open the Make or Zapier tile
At SettingsIntegrations. Authorise the workspace when prompted, choosing the correct workspace explicitly.
In Make or Zapier, add the Zyan app and pick a trigger
Seven are available: successful form submission, booking created, booking status changed, booking no-show, lead created, deal stage changed, and selected workflow dispatch data.
To send data out of Zyan, add a Send to Make or Zapier step
In a Zyan automation.
To start a Zyan automation from outside, use the External event trigger
Publish the automation, then select it in the provider's action.
Both are provider-gated
Make and Zapier require a private or test installation first; public marketplace approval is a separate state. Zyan-side starter recipes stay disabled until you enable them explicitly, and delivery rows marked Needs review — check provider before taking further action are never replayed automatically.
Pausing is not disconnecting
A provider pauses in exactly one place. Tiles that can pause carry a switch; pausing keeps the credentials and takes the provider out of service, and the provider's own settings card then shows no connect form and says Turn it back on under Settings → Integrations. A Pipedream-backed connection pauses per account instead — from the row's menu (Pause notifications for Teams, Pause bookings for Microsoft Calendar) or the mailbox row's switch — and its tile has no switch of its own.
Pausing a telephony provider pauses texting too
Voice and SMS share the provider connection. Pausing Twilio or Telnyx from its tile stops your texting lines as well as your calling, and you are not asked a second time.
Settings reference
| Setting | What it changes | Default |
|---|---|---|
| Tile switch | Pauses or resumes a connected provider without removing its credentials — only on tiles that can pause; a Pipedream-backed connection pauses from its row instead. The label reads paused, on, or not connected. | — |
| Connect | Starts the provider's connect flow — OAuth, a pasted key, or a Pipedream sign-in. | — |
| Disconnect | Removes the connection. Owner or admin only, and refused where something still depends on it. | — |
| Find action | Pipedream connections. Looks up an older provider operation by ID so you can inspect its result. | — |
| Retry original workflow step | Pipedream connections. Re-runs a failed workflow step against the provider, where that is safe. | — |
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| No integrations match | The search term does not match a tile | Search by provider name, or browse the category |
| A settings card has no connect form | The provider is paused from its tile | Turn it back on under Settings → Integrations |
| Texting stopped when you paused a carrier | Voice and SMS share the connection | Resume the provider from its tile |
| You cannot connect anything | Most connections are owner or admin only | Ask a workspace owner or admin |
| A step's action fails although the account is connected | Connecting does not prove write access at the provider | Check the selected resources and the provider's own permissions |
| A reconnect is refused | It needs the original consenting actor and a verified identity | Create a new connection instead |
| A Make or Zapier recipe is not running | Zyan-side starter recipes stay disabled until enabled | Enable it explicitly on both sides |