Automations
Read the conversation. Update the record. No one touches it.
A visual builder where a workflow starts from something that actually happened (a call going through Voice QA, a lead landing, a form arriving) and finishes with your CRM already correct.
Twelve triggers
A workflow starts from something that happened.
Not a schedule you hope lines up with reality. The events your platform already emits are the events a workflow can start from.
Assistant activity
A session starting or ending, a reply being rated, or the assistant finishing collecting the information you asked it for.
Records appearing
A contact created from a conversation, or a lead created anywhere in the CRM.
Calls and tickets
A call finishing in Voice QA, transcribed or scored, or a ticket being opened.
Outside and on demand
A form submission, an inbound webhook, a schedule, or a person pressing run.
Eighteen actions
What a workflow can actually do today.
Every action listed here runs today. The builder also shows a few blocks that are still being built; the product marks those, and they are not sold here.
- Read and extract
- Pull structured fields out of a conversation or a transcript with AI, and carry them forward as typed variables the next step can use.
- Branch
- Conditions on anything in scope, including the fields you just extracted, so one workflow covers the several ways a conversation can go.
- Loop
- Iterate over a list and run the same steps for each element. Loops can sit inside other loops, and each one keeps track of its own item.
- Find
- Look up a contact by whatever identifier you have, or query for many records at once and act on the set.
- Create, update, remove
- Full write access to contacts, leads and companies: nine actions across the three, so a workflow can finish the job rather than filing a note for someone.
- Move and tag
- Advance a lead to another pipeline stage and apply tags, which is how most of these workflows end.
- Assign work
- Create a task so a person picks up exactly the part that needs a person.
Beyond the platform
And when the work leaves Fineguide.
The built-in builder covers the CRM. For everything past it, such as your billing system, your warehouse or an internal API, the n8n bridge picks up where it stops.
- Use the hosted n8n instance, or point us at one you already run
- Hundreds of integrations on the n8n side, none of which we have to build
- Webhooks on conversations, leads and tickets for anything with an HTTP endpoint
- Workflow runs are part of your plan, so they do not consume credits
- Every run is inspectable step by step, so a failure tells you which step and why
Build one and watch it run.
Start from a trigger you already have, add the two or three steps that follow, and stop doing that part by hand.