Try Your First Automation

Goal: create a company and see one email action and its recorded result. This uses the current synchronous implementation with no extra services. Follow Getting Started, then import the Postman collection.

1. Create an OrganizationCopy Anchor Link

Authenticate and send Create Organization. The collection stores organization_id; your user becomes the owner. Requests below all use:

/api/v1/organizations/{{organization_id}}/

2. Create the RuleCopy Anchor Link

Send Create Company Email Automation, or POST automations/ with:

{
  "name": "Notify accounting",
  "trigger": "company.created",
  "action_type": "send_email",
  "action_config": {
    "to": ["accounting@example.com"],
    "subject": "New company",
    "body": "A company was added to Bubllio CRM."
  },
  "is_active": true
}

Expect HTTP 201 and a rule ID. Postman saves it as automation_id. This only saves the rule; it sends no email yet.

3. Create a New CompanyCopy Anchor Link

Send Create Company, or POST companies/ with:

{
  "name": "Automation demo company",
  "lifecycle_stage": "lead"
}

Expect HTTP 201. The save emits company.created; the active rule executes before the request finishes. With the checked-in console backend, inspect the terminal running runserver for the email. No SMTP account is needed.

Existing companies are not replayed when the rule is created. More matching active rules produce more action attempts.

4. Inspect HistoryCopy Anchor Link

Send List Automation Runs, or GET automations/runs/. Look for the rule ID and new company ID in payload, with status: success. The list is newest first. For a failed action, inspect error_message.

Company creation returning HTTP 201 alone does not prove the action succeeded. A console success means the action completed, not inbox delivery.

5. Try the Manual Action TestCopy Anchor Link

Send Test Automation, or POST automations/{{automation_id}}/test/ with:

{
  "payload": {
    "test": true,
    "source": "postman"
  }
}

This executes the action again and writes another run. It does not create a company or verify event dispatch. It also runs inactive rules. HTTP status is 201 even for a recorded failure; check status and run.error_message. The payload is logged, not substituted into email content.

Common SurprisesCopy Anchor Link

For implementation details and reliability limits, read Automations. For the planned visual experience, read the workflow roadmap.