Export a workflow
Use export in the editor to download JSON. The document describes steps and conditions; it does not transfer access to your connected accounts.
Prepare a valid file
Use the JSON example, schema and authoring guide available in Resources. They define the expected structure for preparing a workflow with another AI or from a template.
Import and reconnect
Import JSON from Automations, review its steps and select accounts. The imported workflow remains paused until reviewed. Permissions are checked again before activation and execution.
What to give an external AI
Download the schema, example and guide below. Supply all three with your business goal, trigger and expected outcome. Ask for a schema-compliant file without invented modules or account IDs.
Using this Keyful schema and example, prepare a daily arrivals briefing workflow. Use only documented node and action types. Leave accounts to reconnect in Keyful. If a required action is absent from the supplied catalog, say so instead of inventing its identifier.
Review the import before activation
JSON describes a procedure, not an authorization. Select accounts in Keyful and inspect every action field. An email address in a template can be technically valid but still be the wrong recipient.
- Trigger matches your event or schedule.
- Links connect the intended steps.
- Accounts belong to the correct scope.
- Test recipients replace production recipients.
- Simulation and the authorized real test give the expected result.
Keep a version you can return to
Save the validated export with a date and descriptive name. Add a short record of the goal, owner, accounts to reconnect and tests performed.
Review free-text fields before sharing. Connection secrets are excluded, but text, addresses or instructions you entered may still contain private information.
Attach a workflow test recordPrepare a workflow with your own AI.
The example describes a portable procedure. Reconnect accounts in Keyful; imports remain paused until reviewed.