Skip to main content

​
Start with a real outcome

The best workflows start with a clear result, not just a list of tools. Before creating the workflow, decide:
  • what event should start it
  • what outcome should happen at the end
  • how you will tell whether it worked
Good first outcomes are usually easy to verify, such as:
  • sending a Slack message
  • creating a row in Google Sheets
  • generating a summary from incoming content
  • updating a page or record in another app
If the result is easy to check, the workflow is easier to debug too.

​
Create the first draft

Open Home and describe your use case in a prompt. For example:
  • When a new form submission arrives, send a Slack alert with the lead details
  • Every weekday morning, summarize new support emails and send a digest
  • When a webhook is received, write the important fields into Google Sheets
Then send the prompt to create the workflow. Workflow Machine uses AI to turn that prompt into a starting workflow draft with the trigger and steps it thinks best match the use case.

​
Start from scratch does not mean doing everything manually

Creating a workflow from scratch still does not require you to assemble every part by hand from the beginning. The important part is that you are starting from your own use case instead of a template. The AI-generated draft is a starting point that reflects your prompt, and you can then edit it however you want.

​
Name and organize the workflow clearly

Once the workflow exists, give it a name that reflects the business job it performs. Good names describe the process clearly:
  • New lead follow-up
  • Daily support digest
  • Webhook to spreadsheet log
Avoid names that only describe the tools involved. A workflow should still make sense when you revisit it later in the Workflows page.

​
Keep the first version practical

The goal of the first version is not to cover every edge case. Aim for:
  • one clear trigger
  • one useful output
  • a short set of steps
  • a result you can test quickly
You can always improve the workflow after you confirm that the basic path works.

​
A good first workflow shape

Most first workflows are easiest to build when they follow a simple pattern:
  1. something happens
  2. the workflow receives or checks the input
  3. the workflow produces one useful result
If you can explain your workflow in one or two sentences, you are usually starting in the right place.