Creating your first automation

Automations let DispoStack do repetitive follow-up work for you — automatically. Here is how to build your first one in under two minutes.

What is an automation?

An automation watches for something to happen in DispoStack (called a trigger), checks an optional condition, and then takes an action on your behalf. For example: "When a new lead comes in from the website, create a follow-up task due tomorrow."

Step 1: Open Automations

Go to Automations in the left sidebar (between Transactions and Settings). If you have no automations yet, you will see a starter recipes panel.

Step 2: Use a recipe or build from scratch

Starter recipes are pre-filled automations you can add with one click:

• New website lead → create follow-up task — When a lead arrives from your website intake form, automatically create a high-priority follow-up task due in one day.
• Lead qualified → create offer task — When you mark a lead as Qualified, create a task to prepare an offer.
• Contract signed → notify webhook — When a transaction enters the Contract Signed stage, fire a webhook to your external system.

Click a recipe card to create it instantly and land on the edit page where you can adjust the details.

To build from scratch, click New automation in the top-right.

Step 3: Fill in the three steps

The builder walks you through three steps:

1. 1Trigger — Choose which event fires this automation. Give it a descriptive name at the top.
2. 2Condition — Optionally narrow down when it runs. For example, only fire when the source field equals "website".
3. 3Action — Pick what happens and configure the details (task title, due date, assignee, webhook URL, etc.).

Step 4: Save and enable

Click Create automation. It lands on the detail page showing the edit form and run history below. The automation is enabled by default — you will see the blue toggle on the list page. You can disable it any time by clicking the toggle.

Checking if it worked

After your automation fires, go to Automations → click the automation name → Run history. Each run shows a green checkmark (success), red X (error), or dash (skipped — condition was not met). Errors include a short message explaining what went wrong.