Skip to main content

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.

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.

No Code Required

Build automations visually with drag-and-drop

Built-In

Native integration — no external tools needed

100+ Connectors

Connect to Gmail, Slack, HubSpot, Sheets, and more

​
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 WorkflowsExternal Tools (Zapier, n8n, Make)
SetupAlready integrated — just create a workflowRequires webhook registration and external account
TriggersNative call events with full contextReceives webhook payload only
CostIncluded in your planSeparate subscription
Connectors100+ apps via ActivepiecesVaries by platform
Best forMost automation needsNiche apps not in Activepieces catalog
Start with built-in workflows. Only use external tools if you need a specific connector that isn’t available natively.

​
Creating an Automation

1

Navigate to Workflows

Go to Build → Workflows in the sidebar.
2

Open a Collection

Select an existing collection or create a new one. Collections organize related workflows and can be linked to VoiceFlows.
3

Create a New Workflow

Click New Workflow. The visual workflow builder opens.
4

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
5

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.).
6

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.
7

Test

Run a test to verify the workflow works end-to-end.
8

Publish

Toggle the workflow on. It’s now live and will trigger automatically.

​
Linking Workflows to VoiceFlows

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

Open Your VoiceFlow

Navigate to Build → VoiceFlows and click on the VoiceFlow.
2

Go to Post-Call Settings

Click the Post-Call tab in VoiceFlow settings.
3

Select a Workflow Collection

Choose the collection containing your automation workflows.
4

Save

All published workflows in that collection now trigger on events from this VoiceFlow.
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.

​
Managing Connections

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

Open the Collection

Navigate to Build → Workflows and click on a collection.
2

Click Connections

View and manage OAuth connections and API keys for external services.
3

Add a Connection

Click Add Connection, select the service (e.g., Gmail, Slack, HubSpot), and authorize access.
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
Use run history to debug failed automations. Click into the failed step to see the exact error message and input data.

​
Common Automation Recipes

Trigger: Call CompletedActions:
  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.
Trigger: Call CompletedActions:
  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.
Trigger: Call CompletedActions:
  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.
Trigger: Call CompletedActions:
  1. Add a row to Google Sheets with: date, contact name, phone, duration, outcome, summary
Result: Automatic call log spreadsheet for reporting.
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.

​
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 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)
  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

PlatformBest For
n8nSelf-hosted, full control, complex logic
ZapierSimple automations, 5000+ app integrations
MakeVisual workflows, advanced conditional logic
External tools receive the same webhook payload as built-in workflows. See Webhooks for the payload format and event types.

​
Best Practices

Use built-in workflows first. They have native access to call data and don’t require external accounts or webhook setup.
Test with test calls. Always run a test call to verify your automation before going live.
One workflow per automation. Keep each workflow focused on a single task rather than building one complex mega-workflow.
Monitor run history. Check workflow runs regularly to catch and fix failures early.

​
Next Steps

Workflows

Learn more about workflow collections and triggers

Webhooks

Set up webhook endpoints for external tools

MCP Integration

Give your assistant access to tools during calls