> ## Documentation Index
> Fetch the complete documentation index at: https://docs.eolasflow.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Automation

> Automate post-call actions and business processes with EolasFlow's built-in workflow engine

EolasFlow has a built-in visual workflow engine for automating business processes around your calls. Build automations that trigger when calls complete, sync data to your CRM, send notifications, and more — all without writing code.

<CardGroup cols={3}>
  <Card title="No Code Required" icon="code-slash">
    Build automations visually with drag-and-drop
  </Card>

  <Card title="Built-In" icon="bolt">
    Native integration — no external tools needed
  </Card>

  <Card title="100+ Connectors" icon="link">
    Connect to Gmail, Slack, HubSpot, Sheets, and more
  </Card>
</CardGroup>

## Built-In Workflows vs External Tools

EolasFlow includes a native workflow engine powered by Activepieces. For most automations, you don't need external tools like n8n or Zapier — everything is built in.

|                | Built-In Workflows                          | External Tools (Zapier, n8n, Make)                 |
| -------------- | ------------------------------------------- | -------------------------------------------------- |
| **Setup**      | Already integrated — just create a workflow | Requires webhook registration and external account |
| **Triggers**   | Native call events with full context        | Receives webhook payload only                      |
| **Cost**       | Included in your plan                       | Separate subscription                              |
| **Connectors** | 100+ apps via Activepieces                  | Varies by platform                                 |
| **Best for**   | Most automation needs                       | Niche apps not in Activepieces catalog             |

<Tip>
  Start with built-in workflows. Only use external tools if you need a specific connector that isn't available natively.
</Tip>

## Creating an Automation

<Steps>
  <Step title="Navigate to Workflows">
    Go to **Build → Workflows** in the sidebar.
  </Step>

  <Step title="Open a Collection">
    Select an existing collection or create a new one. Collections organize related workflows and can be linked to VoiceFlows.
  </Step>

  <Step title="Create a New Workflow">
    Click **New Workflow**. The visual workflow builder opens.
  </Step>

  <Step title="Choose a Trigger">
    Select what starts the automation:

    * **Call Completed** — fires when a call ends (includes transcript, recording, summary, outcome)
    * **Call Started** — fires when a call begins
    * **Agent Event** — fires on custom events during calls
    * **Schedule** — fires on a time schedule (hourly, daily, weekly)
    * **Webhook** — fires when an external HTTP request hits the trigger URL
  </Step>

  <Step title="Add Actions">
    Add one or more actions — what the workflow does when triggered. Browse connectors to find the app you need (Gmail, Slack, HubSpot, Google Sheets, HTTP Request, etc.).
  </Step>

  <Step title="Configure Each Step">
    Map data from the trigger into your action fields. For example, map the call summary into a Slack message, or the customer phone into a CRM lookup.
  </Step>

  <Step title="Test">
    Run a test to verify the workflow works end-to-end.
  </Step>

  <Step title="Publish">
    Toggle the workflow on. It's now live and will trigger automatically.
  </Step>
</Steps>

## Linking Workflows to VoiceFlows

Workflows are grouped into **collections**. To automate actions for a specific VoiceFlow:

<Steps>
  <Step title="Open Your VoiceFlow">
    Navigate to **Build → VoiceFlows** and click on the VoiceFlow.
  </Step>

  <Step title="Go to Post-Call Settings">
    Click the **Post-Call** tab in VoiceFlow settings.
  </Step>

  <Step title="Select a Workflow Collection">
    Choose the collection containing your automation workflows.
  </Step>

  <Step title="Save">
    All published workflows in that collection now trigger on events from this VoiceFlow.
  </Step>
</Steps>

<Note>
  You can link one collection to multiple VoiceFlows. For example, a "CRM Sync" collection could trigger on calls from both your Sales and Support VoiceFlows.
</Note>

## Managing Connections

Each workflow collection has its own set of connections to external services.

<Steps>
  <Step title="Open the Collection">
    Navigate to **Build → Workflows** and click on a collection.
  </Step>

  <Step title="Click Connections">
    View and manage OAuth connections and API keys for external services.
  </Step>

  <Step title="Add a Connection">
    Click **Add Connection**, select the service (e.g., Gmail, Slack, HubSpot), and authorize access.
  </Step>
</Steps>

Connections are scoped to the collection — workflows in other collections use their own connections.

## Workflow Run History

Track every execution of your workflows:

* Navigate to a collection and click on a workflow
* View the **Runs** tab to see execution history
* Each run shows: trigger event, step-by-step status (success/failure), timing, and output data
* Click a run to inspect individual step inputs and outputs

<Tip>
  Use run history to debug failed automations. Click into the failed step to see the exact error message and input data.
</Tip>

## Common Automation Recipes

<AccordionGroup>
  <Accordion title="Post-Call CRM Update" icon="database">
    **Trigger:** Call Completed

    **Actions:**

    1. Look up contact in HubSpot by phone number
    2. Update contact properties with call outcome and summary
    3. Create a note with the call transcript

    **Result:** Every completed call automatically updates your CRM.
  </Accordion>

  <Accordion title="Slack Notification on Completed Call" icon="message">
    **Trigger:** Call Completed

    **Actions:**

    1. Format message with caller name, outcome, and summary
    2. Send to #sales or #support Slack channel

    **Result:** Your team gets instant visibility into every call.
  </Accordion>

  <Accordion title="Follow-Up Email for Interested Leads" icon="envelope">
    **Trigger:** Call Completed

    **Actions:**

    1. Check if call outcome is "Interested"
    2. If yes, send a personalized follow-up email via Gmail
    3. If no, skip

    **Result:** Hot leads get an email within seconds of the call ending.
  </Accordion>

  <Accordion title="Log Calls to Google Sheets" icon="table">
    **Trigger:** Call Completed

    **Actions:**

    1. Add a row to Google Sheets with: date, contact name, phone, duration, outcome, summary

    **Result:** Automatic call log spreadsheet for reporting.
  </Accordion>

  <Accordion title="Daily Call Summary Report" icon="clock">
    **Trigger:** Schedule (daily at 9:00 AM)

    **Actions:**

    1. Query yesterday's call statistics
    2. Format as a summary report
    3. Send to Slack or email

    **Result:** Daily digest of calling activity without manual effort.
  </Accordion>
</AccordionGroup>

## MCP Tools from Workflows

Workflow collections can also expose **MCP tools** — tools your AI assistant can use during live calls. When a collection is linked to a VoiceFlow and has MCP tools configured, those tools are automatically available to the assistant during calls.

This means your workflows can both:

* **React to calls** (post-call triggers) — automate after the call
* **Power calls** (MCP tools) — provide real-time data during the call

See [MCP Integration](/guides/mcp) for details on how MCP tools work during calls.

## Using External Automation Tools

If you need a connector that isn't available in the built-in workflow engine, you can use external tools via webhooks.

### How It Works

1. Register a webhook endpoint in **Connect → Webhooks** (see [Webhooks Guide](/guides/webhooks))
2. Enable the webhook on your VoiceFlow
3. Your external tool receives call events as HTTP POST requests
4. Build your automation in the external tool

### Supported External Tools

| Platform   | Best For                                     |
| ---------- | -------------------------------------------- |
| **n8n**    | Self-hosted, full control, complex logic     |
| **Zapier** | Simple automations, 5000+ app integrations   |
| **Make**   | Visual workflows, advanced conditional logic |

<Note>
  External tools receive the same webhook payload as built-in workflows. See [Webhooks](/guides/webhooks) for the payload format and event types.
</Note>

## Best Practices

<Tip>
  **Use built-in workflows first.** They have native access to call data and don't require external accounts or webhook setup.
</Tip>

<Tip>
  **Test with test calls.** Always run a test call to verify your automation before going live.
</Tip>

<Tip>
  **One workflow per automation.** Keep each workflow focused on a single task rather than building one complex mega-workflow.
</Tip>

<Tip>
  **Monitor run history.** Check workflow runs regularly to catch and fix failures early.
</Tip>

## Next Steps

<CardGroup cols={3}>
  <Card title="Workflows" icon="sparkles" href="/guides/workflows">
    Learn more about workflow collections and triggers
  </Card>

  <Card title="Webhooks" icon="link" href="/guides/webhooks">
    Set up webhook endpoints for external tools
  </Card>

  <Card title="MCP Integration" icon="plug" href="/guides/mcp">
    Give your assistant access to tools during calls
  </Card>
</CardGroup>