Less repetitive work.
The details a customer gives go straight to the system that needs them. Nobody copies them across by hand.
Flows
Flows is where your business tools meet Plexvia. Connect the services you rely on, then build automated workflows that respond to customers, decide what happens next and act, in Plexvia or in the systems you already use.
Where a flow starts
What a flow can reach
Choose any system to see what moves between it and a flow.
Business integrations
Some connections are built in. Anything with an API can take part through a Call API step and a key you save once. Here is exactly what connects today, and what is planned.
Built into Plexvia. Nothing to install, nothing to configure beyond what you already set up.
Starts a flow, and hears back from it
On your own site, or a WordPress site through the official plugin. A visitor’s message can start a flow, and the flow answers in the same chat.
In the editor: A visitor sends a web-chat message
What enters the flow
Send Message replies in the chat.
Any service with an HTTPS API can take part: your CRM, booking system, order system or a tool you built.
A flow reaches out to it
A Call API step looks something up, sends something new, or changes it. Save the service’s key once in Connection keys: it is encrypted and never shown again.
In the editor: Call API · Plan: Scale, for saved keys
What the step is set to
Later steps branch on what came back, or quote it to the customer.
Send a flow’s details to any address that accepts a webhook. Calling in to start a flow is planned.
A flow posts to it
If a service gives you a webhook address, a Call API step can send it the details as JSON, the moment the flow reaches that step.
In the editor: Call API
What the step is set to
The receiving service takes it from there.
Ways to start a flow that are designed and not yet delivered. Listed so you can plan around them.
Planned: not available yet
Planned. A running flow can already wait and carry on later. Starting a brand-new run on a clock is not there yet.
Use a Delay step inside a flow for follow-ups today.
Workflow builder
Every flow is a trigger, the conditions that decide what happens, and the actions that do it. Write a rule, or let an AI Condition read the conversation and decide. Choose each part below, open any step to see its settings, then run a test.
Business process automation
Four everyday jobs, each a real flow. Pick one and play it, then change what happens and watch the route change.
Plexvia asks for the details a quote needs, sends them to your CRM, and confirms to the customer. If the CRM does not answer, your sales inbox hears about it instead.
Reaches: Your CRM, through its API
Outcome. A new lead in your CRM, and a customer who knows a quote is coming.
A simulation. Nothing is sent, and no real system is contacted.
An AI Switch reads each customer email and picks a path. Billing questions go to billing, booking changes to the front desk, and everything else stays with your agent.
Reaches: Your own mailboxes
Outcome. Billing has it in their inbox, with the whole email.
A simulation. Nothing is sent, and no real system is contacted.
When a customer asks where their repair is, your agent starts a flow that asks for the job number, checks your workshop system and answers with what it found.
Reaches: Your workshop system, through its API
Outcome. The customer knows to come in, and nobody had to check by hand.
A simulation. Nothing is sent, and no real system is contacted.
Plexvia tells the customer help is coming, gathers what a colleague will need, and emails the handover to your support inbox.
Reaches: Your support inbox
Outcome. A colleague has everything in one email, and the customer knows what happens next.
A simulation. Nothing is sent, and no real system is contacted.
Automation and integrations, together
When the connection and the work that uses it live together, there is one thing to set up, one thing to change, and one place to look.
The details a customer gives go straight to the system that needs them. Nobody copies them across by hand.
Your conversations, your team’s inboxes and the services you already pay for take part in the same flow, instead of three separate habits.
The reply, the colleague who needs to know and the record in your CRM all come from one run, so they never contradict each other.
One run
A flow acts the moment it starts, and the same way each time: the same questions, the same handover, the same care.
If a service has an API, a flow can reach it. Edit a draft while the published version keeps running, and see every request in API activity.
Versions
API activity
Availability
Part of the Plexvia private beta. Here is what that means for your workspace.
Flows comes with the rest of the Plexvia private beta. It is not a separate add-on.
Flows is on every plan. AI steps come with Business and Scale. Saved connection keys, flows an agent starts and the Developer API come with Scale.
Starting a flow from a webhook, on a schedule or when a record changes is planned, and marked as planned wherever it appears here.
Keep looking
Every part of Plexvia draws on the same knowledge and the same access rules.
Connect the tool it touches, build the flow once, and let it run. Flows is part of the Plexvia private beta.
Free to start · No card required