Create and Publish an Automation Flow

Build, validate, test and publish one complete Wemblo automation flow.

What this guide helps you do

Build, validate, test and publish one complete Wemblo automation flow.

Who should use it

Workspace owners, managers, automation users and authorized technical users responsible for AI configuration or customer workflows.

Before you begin

  • Use the correct workspace and minimum required role.
  • Use a business-controlled provider account where applicable.
  • Understand provider billing, usage and data settings.
  • Use fictional Pakistan test data.
  • Define human handover before enabling automatic replies or calls.

Main concepts and fields

Concept / FieldMeaning or Use
DraftEditable unpublished flow.
ValidationChecks connected nodes and required fields.
ActivePublished flow available to its trigger.
VersionSaved flow configuration.

Step-by-step instructions

  1. Open Automation Builder.
  2. Create a flow and name it.
  3. Choose the entry trigger.
  4. Add the first response.
  5. Add fields, conditions and actions.
  6. Add fallback and handover.
  7. Validate.
  8. Test every branch.
  9. Activate/publish.
  10. Monitor initial executions.

Test and verification

  1. Run one complete successful path.
  2. Run an invalid or failure path.
  3. Confirm fields, assignment and logs.
  4. Confirm human handover.

Common issues and solutions

IssueWhat to Check
Flow does not startActive status, channel, trigger and entry condition.
Wrong branchField type, stored value and condition order.
Repeated messagesLoop, retries, duplicate event and overlapping flows.
Action failsCredential, endpoint, schema and timeout.
Handover failsTeam, agent and permission.

Security, privacy, consent, cost and provider notes

  • AI-provider charges and Wemblo AI-action usage are separate controls.
  • Do not expose provider keys or customer data in screenshots, tickets or client-side code.
  • Use human review or handover for sensitive, private, regulated, urgent, high-value or final decisions.
  • Do not promise perfect accuracy or guaranteed business outcomes.

Last reviewed: