Skip to main content
Cassidy gives you flexible options for controlling who can access your Workflows, how they are organized, and where they run. This guide covers folder management, permissions, import/export, external deployment, and failure notifications.

​
Organize Workflows with folders

Folders help your team find Workflows quickly and control access at a group level.
1

Create a folder

On the Workflows page, click Create a Folder. Enter a name and choose an access level:
  • Team can edit — anyone in your organization can view and edit Workflows in this folder.
  • Team can view — anyone can view, but only you and explicitly added people can edit.
  • Restricted — only specific people and groups you choose can access the folder.
Create folder dialog showing access level options: Team can edit, Team can view, and Restricted
2

Move Workflows into folders

Drag and drop Workflows from the main list into a folder. You can also move Workflows to the Private section to make them visible only to you.
3

Update folder permissions

Click the … menu on a folder and select Share. Change the access type or add/remove specific people and groups. For each person or group, set Can edit or Can view granular permissions.
Folder sharing dialog showing people and groups with Can edit and Can view permission levels

​
Manage permissions from the editor

You can also update a Workflow’s location and permissions while editing it.
1

Open sharing options

In the Workflow editor, click the … menu and select Organize & Share Workflow under Sharing.
Workflow editor menu showing the Organize and Share Workflow option under Sharing
2

Choose a location

A modal appears showing your Team and Private sections and any folders within them. Select where to save the Workflow, or create a new folder directly from this modal.
Workflow location picker modal showing Team and Private sections with folders
3

Save

Click Save to apply the changes.

​
Import and export Workflows

Exporting lets you save a Workflow as a JSON file for backup or to share with another Cassidy organization. Importing brings a previously exported Workflow into your account.

​
Export a Workflow

1

Open the Workflow editor

Navigate to the Workflow you want to export and click Edit.
2

Export the Workflow

Click the … menu, then under Advanced, select Export Workflow. A JSON file downloads to your computer.
Workflow editor ellipsis menu showing Export Workflow option under Advanced

​
Import a Workflow

1

Start creating a new Workflow

On the Workflows page, click Create Workflow.
2

Select Import Workflow

Instead of choosing Custom Setup or Use a Starting Point, click Import Workflow.
Workflow creation dialog showing the Import Workflow option
3

Upload the JSON file

Upload the Workflow JSON file by dragging it into the upload area or clicking to browse and select it from your computer.
Import Workflow upload area for dragging or browsing a JSON file
4

Complete the import

Click Import Workflow to add it to your organization. The imported Workflow retains all its original actions and configuration.
Import Workflow confirmation showing the imported Workflow ready to use
Imported Workflows may need their integrations reconnected if the target organization uses different accounts.

​
Deploy externally

You can run Cassidy Workflows from outside the platform by using webhook triggers and returning results to your external systems.
1

Use a Webhook trigger

When building your Workflow, select Webhook as the trigger type. Copy the unique webhook URL that Cassidy generates.
2

Configure your external system

Set up your website, app, or automation tool to send a POST request to the webhook URL when the relevant event occurs (e.g., a form submission or a record update).
3

Return results to the caller

You have two options for sending results back:
  • Return results from webhook — toggle this option in the Webhook trigger settings. The Workflow’s output is automatically returned as the HTTP response to the incoming request.
  • Send API Request action — add this action at the end of your Workflow to POST results to a specific endpoint in your system. This gives you full control over the URL, method, headers, and body.
You can also trigger Workflows from Slack, Zapier, or on a schedule — providing flexibility in how you integrate Cassidy with your existing stack.

​
Set up failure notifications

Stay informed when Workflows encounter errors so you can address issues quickly.
1

Access account settings

Click your name in the bottom-left sidebar, then click the settings icon next to your name.
Sidebar showing the settings icon next to your name
2

Open Workflow Notifications

In Account Settings, click Workflow Notifications.
Workflow Notifications settings page showing frequency options
3

Configure default notifications

Choose how you want to be notified about failures for Workflows you create:
FrequencyDescription
Daily SummaryOne digest of all failures per day
Hourly SummaryOne digest per hour
ImmediateInstant notification for every failure
OffNo notifications
Click Save to apply.
4

Subscribe to other Workflows

To receive alerts for Workflows you did not create, click + Add Subscription.
Add Subscription button on the Workflow Notifications page
5

Select a Workflow and frequency

Click the No workflow selected dropdown and choose the Workflow you want to be notified about. Select a notification frequency and click Save.
Workflow dropdown showing available Workflows to subscribe to
6

Manage existing subscriptions

From the subscriptions list, you can search your active subscriptions, update the notification frequency, or remove subscriptions you no longer need.
Notification subscriptions list showing active subscriptions with frequency and remove options
You can also subscribe to failure notifications directly from within any Workflow by clicking the … menu and selecting Failure Notifications.
Workflow editor menu showing the Failure Notifications option
When a Workflow fails, you receive a Workflow alert containing the error details, the affected Workflow name, and an error summary. The notification includes links to Edit this Workflow (to fix the issue) and View Failed Workflow Run (to inspect the specific run).
Workflow failure notification showing error details with links to edit the Workflow or view the failed run

​
Next steps

Configure data retention

Control how long Workflow run history is stored.

Use secret keys

Securely store API keys and passwords for use in Workflow actions.

Manage roles and groups

Set up teams and roles to streamline Workflow permissions.

Build a Workflow

Go back to creating and configuring Workflows.