Start from an official Zapier JSON export, let Samsarix propose compatible steps, then review mappings, reconnect credentials, and test beside the original before cutting over.
Team and Enterprise owners can download Zap workflow JSON from Settings → Security and data. Other users can request their account-data export and locate Zapfile.json in the downloaded archive.
Zapier limits the dedicated workflow import/export feature to Team and Enterprise.
Navigate to Spirals → Import and upload the compatible JSON. Samsarix parses recognized triggers and actions, then proposes a Spiral rather than publishing it automatically.
Unsupported or ambiguous steps require review instead of being silently invented.
Compare every proposed trigger, action, filter, path, and field mapping with the source Zap. Reconnect each app credential in Samsarix and replace any unsupported step before testing.
The source export does not transfer live app credentials or guarantee feature parity.
Run the proposed Spiral with non-production sample data. Verify outputs, retries, and AI usage while the original Zap remains active and authoritative.
A successful import is not a successful production cutover.
Enable the Samsarix trigger only after side-by-side results match. Disable the corresponding Zap after a monitored overlap window, and keep the original export for rollback.
Set a monthly spending limit in Settings and choose retries or continue-on-error for each step before activation.
| Feature | Zapier | After Samsarix import |
|---|---|---|
| Migration artifact | Official workflow or account-data JSON export | Compatible JSON parser with a review step |
| Agent model | AI by Zapier, Copilot, tools, and Agents | 24 named agents, each with one job, assigned per step |
| Failure response | Error handlers, troubleshooting, and autoreplay | Per-step retries, continue on error, a fallback Spiral and quality checks that can fail, skip or escalate |
| Usage visibility | Task and activity allowances with AI multipliers | AI usage billed in dollars, with a monthly spending limit you set that can stop it |
| Run visibility | Run history and product-specific activity views | Run history with the status and log of every step |
| Cross-run context | Tables, knowledge, and live data sources | Agent memory you can view and export |
Not automatically. The importer proposes recognized trigger, action, filter, and field mappings. Review every result, replace unsupported steps, reconnect credentials, and test before cutover.
Yes. Credentials are never transferred in the workflow JSON. Reconnect each app in Samsarix, and verify that every source action has an exact equivalent or an intentional API-based replacement.
Zapier execution history stays in Zapier. Samsarix starts fresh with its own run history. If you need historical data, export it from Zapier before canceling.
Yes. Keep Zapier authoritative while you test a Samsarix proposal with bounded sample data. Cut over only after the results match and you have reviewed credentials, unsupported steps, costs, retries, and rollback.
The import will flag any zap steps that don't have a direct Samsarix equivalent. You can either simplify those steps or use Samsarix's API integration to handle custom logic.
Review a proposed Spiral, verify every mapping, and choose the cutover. Start on the Free plan without a credit card.