Skip to content

FAQ

Frequently asked questions

What can I automate with Stacksync workflows?

Anything triggered by a data change. Common patterns: send a Slack message when an opportunity is marked won, enrich a new Salesforce lead via Clearbit then route to the right rep, sync a Postgres row update to NetSuite with custom validation, fire a webhook to your billing system on every subscription upgrade. Workflows run on real-time triggers from any connected system and chain together as many steps as you need.

How is this different from Zapier or n8n?

Zapier and n8n charge per-run and queue events through a generic orchestrator — costs scale linearly with volume and latency adds up. Stacksync runs workflows on the same streaming sync infrastructure that powers two-way sync, so latency is sub-second and pricing is per-connection rather than per-event. Stacksync also natively handles bidirectional state — Zapier is one-way only. For high-volume CRM and ERP automation, Stacksync usually replaces 3 to 5 Zaps with one Stacksync workflow.

Can workflows trigger on database changes?

Yes — database change-data-capture is a first-class trigger. Subscribe to Postgres logical replication, MySQL binlog, MongoDB change streams, DynamoDB Streams, or SQL Server CDC, and your workflow fires on every INSERT, UPDATE, or DELETE within milliseconds. You can filter triggers by predicate (only rows where status=active, only customers in Europe, etc.) to keep workflow runs targeted.

Do workflows support conditional logic and branching?

Yes. Each workflow step has a configurable condition (visual editor or JavaScript expression). Branching, parallel forks, lookup tables, loops with iteration limits, and dynamic step-to-step variable passing are all supported. You can also call out to your own code (JavaScript or Python) inline when the built-in steps do not cover your case.

What happens when a workflow step fails?

Failed steps retry with exponential backoff for up to 7 days. If retries are exhausted, the workflow run lands in the dead-letter queue with full context (input payload, step outputs, error message). You can fix the underlying issue and replay the run from any step. Workflows are durable — a server restart does not lose in-flight work.

Can I version-control and deploy workflows like code?

Yes. Workflow definitions can be exported as YAML and version-controlled in Git. The Stacksync CLI deploys workflow changes via CI/CD pipelines, with environment-specific overrides for dev/staging/prod. Workflow definitions are diffable, reviewable, and auditable. For visual editing teams, the dashboard pushes changes to Git as commits so a PR can be raised before changes go live.