Zapier Integration

SchemaStack integrates with Zapier to connect your data to 7,000+ apps — no code required. Send SchemaStack data to Mailchimp, Slack, Google Sheets, and more.

Two Ways to Connect

1. Outbound Webhooks (Push Data Out)

Send selected rows from SchemaStack to Zapier using webhooks:

1. In Zapier, create a new Zap with Webhooks by Zapier → Catch Hook as the trigger
2. Copy the webhook URL
3. In SchemaStack, add this URL as a webhook on your view (View Properties → Webhooks)
4. Select rows and use "Send to webhook" to push data
5. In Zapier, map the fields to your destination app

Best for: Manually triggered exports, batch operations, ad-hoc data pushes.

2. Native Zapier Integration (Automated)

Use the SchemaStack Zapier app for automated triggers and actions:

Triggers (Data → Zapier)

• New Row — Triggers when a row is added to a table
• Updated Row — Triggers when a row is modified (requires updated_at column)

Actions (Zapier → Data)

• Create Row — Add a new row to a table
• Update Row — Modify an existing row by ID

Searches

• Find Row — Look up a row by field value

Best for: Automated workflows, real-time syncing, two-way integrations.

Setting Up the Native Integration

1. Get Your API Key

1. Go to Admin Console → Workspace Settings → API Keys
2. Create a new API key with appropriate permissions
3. Copy the key (starts with sk_)

2. Connect in Zapier

1. Search for SchemaStack in Zapier's app directory
2. Click Connect
3. Enter your API key, organisation slug, and workspace slug
4. Test the connection

3. Create Your First Zap

Example: New customer → Slack notification

1. Trigger: SchemaStack → New Row → Select "customers" table
2. Action: Slack → Send Channel Message
3. Map fields: just signed up ()

Example: Form submission → SchemaStack row

1. Trigger: Typeform → New Entry
2. Action: SchemaStack → Create Row → Select "leads" table
3. Map form fields to table columns

Dynamic Fields

The SchemaStack Zapier integration automatically loads your table's columns as dynamic fields. When you select a table, Zapier fetches the column definitions and presents them as form fields with the correct types.

Required Timestamp Columns

For Zapier triggers to work reliably, your tables should have:

Column	Timestamp Behavior	Used by
created_at / createdAt / created	On insert (created_at)	New Row trigger — sorts by this to find newest rows
updated_at	On update (updated_at)	Updated Row trigger — sorts by this to find recently changed rows

Set these up in the Data Platform: select the column → Properties panel → Timestamp Behavior.

The New Row trigger looks for columns named created_at, createdAt, or created (in that order). If none are found, it falls back to any timestamp column.

UUID Primary Keys

Tables with UUID primary keys must have a timestamp column for the New Row trigger. Integer/auto-increment PKs work without it since new rows always have the highest ID.

Limitations

• Polling interval: Zapier checks for new/updated rows every 1-15 minutes (depends on your Zapier plan)
• New Row trigger: For UUID PK tables, requires a created_at column with "On insert" timestamp behavior
• Updated Row trigger: Requires an updated_at column with "On update" timestamp behavior
• API key permissions: The API key must have read/write access to the tables you want to use
• Rate limits: Standard SchemaStack API rate limits apply