Import and export Workflows
Use Export Workflow to download a portable JSON configuration. Import Workflow creates a separate Draft from that file in the currently selected FastHook team. Import does not replace the Workflow you have open or activate the new copy.
For a quick copy within your team, the Workflows list also offers Duplicate.
Export a Workflow
- Open the Workflow in the editor.
- Finish editing, save any pending changes, and wait for saving to complete.
- Open the three-dot More Workflow actions menu.
- Select Export Workflow and save the downloaded JSON file.
Export reads the saved configuration. It does not run the Workflow or change its activation status.
What the file contains
| Included | Needs separate setup or verification |
|---|---|
| Workflow name, Steps, routes, mappings, and conditions | Connected provider accounts and their permissions |
| Trigger definition and non-secret settings, when configured | Account binding, webhook authentication, and provider subscriptions |
| Referenced reusable transformation code, filter definitions, and Destination configuration | Removed credentials and transformation environment values |
| Configured schedule, when present | Destination-environment timing and account/resource access |
The portable file uses the FastHook Workflow format, version 1. A raw API response from GET /v1/workflows/:id, a run-history download, or a file exported by another automation product is not this import format.
Export removes connected-account bindings and recognized credential fields. Transformation environment key names can be included, but their values are not exported. Fixed configuration, transformation code, recipient addresses, resource IDs, and ordinary text can still be present. Review the JSON before sharing it; removal of recognized secret fields is not a guarantee that every value you typed is public.
The file contains configuration, not run history, Action test results, stored payloads, or a backup of external app data.
Import as a Draft
- Open the Workflow editor. From the Workflows list, Create workflow opens that workspace; you do not have to create an empty Workflow first.
- Open More Workflow actions → Import Workflow.
- Choose the exported file under Workflow JSON file. The maximum size is 2 MiB.
- Review the Name and the displayed counts of Steps, routes, and reusable resources.
- Select Import as Draft.
The editor opens the new Draft. FastHook creates new Workflow, Step, route, and reusable-resource identities and updates the graph's internal references. An imported webhook gets a new Source URL. The original Workflow is unchanged, and the imported Workflow does not start normal execution automatically.
Complete the imported configuration
Open the Trigger and every Step to review:
- Accounts: connect or select accounts available in the destination team.
- Resources: choose the intended spreadsheets, channels, folders, projects, and other app resources. A copied fixed resource ID can still point to the original resource.
- Secrets: restore the required credentials, webhook verification settings, and transformation environment values through their normal editors.
- Webhook sender: use the new Source URL when the copy should receive its own events.
- Schedule: confirm the timing and timezone before activation.
- Mappings: obtain a fresh Trigger sample and check the data available to each Step.
Importing configuration does not grant access to the app resources named in it. Use Environment promotion when moving between development, staging, and production.
Test and activate
Use the Trigger's Test stage and the Steps' Test step controls with destination-environment data. An Action test can make a real external change while the Workflow is still a Draft. Repeating it can repeat that change.
Auto-validate also runs real tests. Opening saved Validation results does not run them again; Check again does. For a route containing Only new items, verify downstream delivery with a normal run rather than relying on its stateless test preview.
When accounts, required settings, and expected results are correct, select Activate or the final editor's Publish. Produce a new Trigger event and check Run history and the result in the destination app.
Resolve an import error
| Message or symptom | What to check |
|---|---|
| Invalid JSON or wrong export format | Choose an unmodified FastHook Workflow JSON export, version 1. |
| File exceeds 2 MiB | Reduce the configuration size and export again. |
| Invalid graph or missing reusable resource | Export the source Workflow again with its complete referenced configuration. |
| Missing account, secret, or target after import | Complete those settings in the new Draft; they are not permissions granted by the file. |
| Trigger data differs from the original | Select a new sample and review the mappings before testing Actions. |
Import creates a new configuration. To investigate or restore the behavior of an existing Workflow, use Workflow change history and versioning and a reviewed change to that Workflow.