Watch the walkthrough
The English interface uses demonstration data. Runs, customers and results shown are simulated; use the subtitle menu for your language. Your plan determines the included monthly automation runs. Runs beyond that allowance cost extra credits at the workspace’s Automation runs rate; current rates are on the Usage page. AI steps such as Custom Prompt, Extract Fields, and MCP Call Tool can use additional workspace credits. The charged amount appears in the run details and Test panel. Graph end: A step with no outgoing connection completes the run successfully. Stop, Return variables, and Webhook respond end the run immediately and need no further connection.
Automation builder — connect triggers and actions
Automations vs. Agent Tools
Automations and Agent Tools are both ways for an assistant to act on outside systems, but at different moments. An automation is a fixed sequence of steps you (or Milian) design in advance — usually started by a background trigger like On Call Completed, though a Live automation can also be attached to an assistant as one callable action during a conversation (see Calling an automation from a conversation below). Either way, it runs the sequence you built, not something decided on the fly. For tools the assistant chooses and runs itself, live, the moment it needs them — looking something up, creating a record — see Agent Tools.Triggers
- On Call Completed — after a voice call ends (with analysis). Requires a specific assistant.
- On Inbound Call — when an inbound call starts.
- Inject input variables — provides assistant variables when a call starts. End with Return variables.
- Email received — when a new inbound email arrives.
- Conversation started / ended — messaging channel open / closed.
- Message received — every inbound message on a channel, not just the first.
- Contact created — a new Audience contact appears. Choose which sources trigger it: Created manually (the only one on by default), CSV / file import, API, and CRM sync. Leaving import and CRM sync off means a bulk import doesn’t fire the automation for every row.
- Incoming Webhook — starts from the secure webhook URL shown in the trigger.
- Booking created / cancelled / rescheduled, Manual, Schedule (soon).
- App events — connected apps such as Gmail or GitHub provide their own available triggers.
Actions (plugins)
Organized as Platform → type → action (Famulor, AI, Time, WhatsApp, Telegram, X, HTTP, Slack, …).- AI: Extract Fields, Custom Prompt
- Time: Delay For / Until, Get Current Date and Time, Convert Timezone, Format
- Logic: Condition, Filter, Switch, Random, Stop, Note, Set variable, Run Code, Loop on Items
- Contacts: Create/Update, Get by phone, List, Add tags/attributes
- Calls: Call Phone Number
- Messaging: SMS, workspace email, Send Email (SMTP) through a saved SMTP connection, channel messages on open conversations, and approved WhatsApp templates to E.164 numbers. The builder shows which actions use workspace messaging credits.
- Knowledge: Add / Delete / Get source
- HTTP / webhooks: HTTP Request, Slack / Discord / Teams Incoming Webhooks, Webhook respond (sync HTTP status/body for inbound webhooks)
- CRM / SMTP / MCP connections: reusable credentials under Automations → Connections. Test Connection verifies an SMTP relay and sends a test message to the configured address. Available integrations are listed in the connection picker.
- Connected apps: choose New connection in Connections to connect an available app. Its supported tools and triggers appear in the builder after connection.
- Airtable actions: List, Find record, Search records, Find or create, Get by id, Create / Create records (batch ≤10), Update, Delete.
- MCP: Call tool — connection + tool multi-select (or all) + agent prompt with flash variables; the agent picks the tool and fills arguments
- Variables: Return variables (for
call.variables)
Example automations
A trigger and a couple of actions are usually enough:Organizing automations
Automations support free-form tags for filtering and show the selected assistant when a trigger is assistant-specific. Create or update them through the UI,POST/PATCH /api/v1/automations, or MCP (create_automation / update_automation).
The switch in the Status column turns an automation on (Live) or off (Paused). A draft stays a draft until you turn it on. When something is missing, such as a connection, an assistant or a required field, the switch moves back and tells you what to fix. Viewers see the switch but cannot change it.
Duplicate on an automation copies every step and setting into a new draft. The copy stays off until you turn it on, so a live automation does not send twice. Inbound webhooks get a new secret, and the copy does not share a live app-event subscription. It also does not add a second assistant tool; connect the copy yourself if an assistant should call it. If the original runs when a call ends for an assistant, leave the copy as a draft until you choose which one should stay connected.
Optional
name replaces the default name, which is the original name plus ” (Copy)”.
Folders, templates and sharing
Templates, export, import and share links are for direct Famulor workspaces on app.famulor.io. Reseller customer workspaces and custom domains don’t show them, and the API and MCP answer403 in a reseller customer workspace.
Folders
Group related automations in folders, for example one folder per client or location. In Automations, choose New → New folder, then use Move to folder… in an automation’s ⋯ menu. Folders are one level deep and their names are unique in the workspace. The list shows folders first; open one with its arrow. + on a folder row creates a new automation directly in that folder. Searching or filtering by tag shows the matching automations from every folder, each with its folder name. Deleting a folder never deletes automations: they move out of the folder and keep running.
Every automation in
GET /api/v1/automations carries its folder_id. Add ?folder_id=<id> to list one folder, or ?folder_id=none for automations outside folders. Send folder_id: null to move an automation out of its folder. Moving never changes whether an automation is on or off.
Start from a template
New → Start from template opens the template gallery: ready-made automations for calls, bookings, leads, messaging, CRM and team alerts. Each template shows its steps and the apps it uses. Use template creates a draft, optionally in a folder, and opens it in the editor. Steps that still need your own account, phone number, assistant or recipient are marked there; fill them in, then turn the automation on.
Search with
query and filter with category (calls, bookings, leads, messaging, crm, team). The detail lists every step in run order and needs_setup, what to fill in after using the template.
Export and import
Export in an automation’s ⋯ menu downloads it as a.famulor-automation.json file. Import next to New creates a draft from such a file, in this or another workspace.
An import is always a draft and gets a new inbound webhook secret. needs_setup in the response, and the editor after the import, list every step that needs an account, number, assistant or key again. Files can be up to 512 KB. Automations run by a Milian Mission cannot be exported or shared; edit the Mission instead.
Send
{ "file": … } with optional folder_id and name, or the exported file itself as the request body.
Share as a template link
Share… in an automation’s ⋯ menu creates a link. Anyone who opens it sees the name, the description and the steps, and can add a copy to their own workspace with Use template after signing in. The copy is a draft and follows the same rules as an export: no connections, no keys. After you change the automation, click Update link: the link stays the same and shows the new version. Stop sharing turns the link off at once; sharing again later creates a new link. The link always points to app.famulor.io.{token} is the last part of the link (…/automations/share/{token}); the MCP tool also accepts the full link. Reading needs automations:read, changes need automations:write (or the legacy calls:read / calls:write), and the workspace plan must include Automations.
Tidy up the canvas
Use Tidy up beside the zoom buttons to arrange the whole automation from left to right: every branch gets its own row, thetrue branch of a Condition sits above the false branch, the steps of a Loop on Items sit below its Done branch, and a connection that skips ahead runs on a straight line. Only positions change; steps, settings, connections and branches stay as they are. Click Save to keep the new layout.
You can also ask Milian to “tidy up this automation”. In the editor, Milian arranges your current draft, including unsaved steps.
To arrange a saved automation without opening the builder:
No request body is needed. The response reports the automation ID, whether it was saved, and the number of steps and connections; get the automation afterwards to read the new positions.
Runs & failure alerts
The list page has Automations and Runs tabs. Use Alert settings to set a workspace inbox for failed runs and toggle alerts on/off. The Runs tab lists every run in the workspace. Filter by status, search by automation name, and open a run to go straight to its details. Inside an automation, the Runs tab shows that automation’s run history next to the selected run:- Status, duration and credits, plus what started the run and the trigger data it received.
- Every executed step in order, with its input (the step’s configuration), output, error and duration. Steps inside Loop on Items appear once per item.
- Show in builder jumps from a failed step straight to that step on the canvas.
- A run that is still going updates live, and Run now opens the new run right away. A run always uses the last saved version of the automation.
When no custom email is set, alerts go only to owners and admins of the affected workspace. To include a support inbox, add it explicitly in Alert settings. You can enable or disable failure alerts for each automation.
Calling an automation from a conversation
An assistant can call an automation as a tool while a conversation is still in progress, not only once it ends. Under Assistant → Settings → Automations → During conversation, create an assistant-callable automation and describe, in plain language, when the assistant should use it — a free-text field the assistant reads before deciding to call it. The link connects automatically; build out the automation’s steps, map its response, then switch the automation Live, since the assistant only calls automations that are Live. This works the same way across voice, web chat, messaging, and email conversations, and an assistant can have more than one callable automation, each with its own description. Creating or unlinking one is an owner or admin action. It’s separate from On Call Completed and the inbound triggers above, which fire outside the conversation instead of being called by the assistant itself. For a single action in a connected app, such as adding a spreadsheet row, you don’t need an automation. An app action tool (Beta) gives the assistant the action’s fields directly and skips the extra AI step that pulls values out of a free-text request.Assistant webhook binding
In the assistant Webhook card, choose Automation delivery and select an On Call Completed automation, or keep a custom HTTPS URL.Troubleshooting
A WhatsApp step fails to send. WhatsApp Send Message only works inside an already-open conversation (Meta’s 24-hour service window). To reach someone outside it, use Send WhatsApp Template instead, and confirm that template is already approved for the sender you selected. See WhatsApp for the full window and approval rules. A step fails with an invalid number. Actions expect E.164 (+<country code><number>) — add a country code before passing a national-format number through.
A connector step fails on every run. The underlying connection is likely disconnected or its token has expired. Reconnect it under Automations → Connections.