Describe a workflow in plain language and Hoppflow builds it as a set of steps you can edit. Every step that sends or changes something outside Hoppflow waits for approval in Inbox, so an automation never acts on its own.
Before you begin
- Building and changing automations needs the Manage automations permission. The Owner, Admin, Co-founder, Operations, Delivery lead and Engineering presets include it. The Member preset does not.
- Your plan limits how many automations the workspace can have.
- Only the automation's owner can change or activate it, and whoever activates it becomes its owner. Every run acts as the owner, whoever starts it. Teammates can open the automation, Test it and Run now, but Activate is turned off for them with "Only its owner can activate this automation".
Build from a description
-
Start a new automation
Open Automations and choose New automation. To start from a ready-made flow instead, choose Templates, then Use template on a card. A template card shows what it needs, or "No setup needed".
-
Describe the workflow
Under "What should your agents run?", describe what should happen and choose Build automation. You can also pick one of the ideas shown, or build it yourself step by step.
-
Let Hoppflow build it
Wait while "Building your workflow…" finishes. The steps appear on the canvas.
-
Edit the steps
Select a step to edit it. Add steps from the blocks rail, where Search blocks… finds a block by name. To change the whole flow at once, type in Describe a change to make and choose Rebuild.
-
Name it
Give the automation a name of up to 60 characters. Drafts save automatically, so there is no Save button.
-
Resolve the checklist
Work through the checklist until it reads Ready to activate. For any app marked Not connected, choose Connect.
-
Test the whole flow
Choose Test in the command bar. A passing test reads "Ran end-to-end, nothing sent". See Test, run and cap.
-
Activate it
Choose Activate. If Hoppflow asks you to confirm the Credits the automation may use per run, confirm in Activate this automation?.
A description that works well:
Create an automation that reviews our connected customer records every morning, finds accounts at risk, and drafts an update for the account owner. Treat an overdue renewal or an unresolved escalation as a risk, and use the source already connected in Hoppflow.Draft any message that goes outside the company and send it to Approvals first, and never change external data without approval. Name each step and say what sets it off.
Choose the right step type
| Step | What it does | Main fields |
|---|---|---|
| Trigger | Decides how the automation starts. See Triggers and schedules. | How it starts |
| Tool | Reads from or writes to a tool. Every write waits for approval. | A guided form, plus Tool identity & raw JSON for the raw parameters |
| Agent | Gives an AI agent a goal to work on. | Goal, Capability (optional), Max steps (1 to 25), Model, Search the web (on by default) |
| Approval | Pauses the run for a person to review. | What you'll review, Risk (Low, Medium, High) |
| Shape data | Reshapes data between steps. | Expression |
| Decision | Sends the run down one of several branches. | A condition for each branch |
| Loop | Repeats steps for each item in a list. | Loop over, Each item is called, Max items (1 to 25), For each item, do |
Every step except a trigger or a decision also has Only run when, for a condition, and Remove step.
Rules for decisions and loops
- A decision needs at least two branches, and exactly one of them must have a blank condition to act as the fallback.
- Steps inside a loop must be read-only: an agent, a read tool or a shape data step. Put any send or approval after the loop.
Connect the apps an automation needs
The checklist lists each app the automation uses as Required, Connected or Not connected. A missing app does not block activation. Hoppflow asks whether to activate without it, and you can choose Activate anyway. The step that needs the missing app then files a task for you instead of sending.
Store a secret for an HTTP step
Use Settings > Secrets to store an encrypted key, such as an API token. Reference it in an HTTP write step as {{secret:NAME}}.
- The name must use uppercase letters, digits and underscores, up to 64 characters, for example
STRIPE_KEY. - A secret works only in the step's headers or body, never in its URL.
- The value is never shown again after you save it.
- Deleting a secret stops the automations that use it from sending until you add it again.
Creating and deleting secrets is limited to the Owner, Admin, Co-founder and Operations presets.
Create from chat, duplicate or delete
- From chat. Ask the company brain to draft an automation. It saves a draft only, which you then open, test and activate.
- Duplicate. A copy is named "<name> (copy)".
- Delete. Type the automation's name to confirm, then choose Delete automation.