Flows

Connect your tools. Automate the work between them.

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.

Private beta

Where a flow starts

FlowsTrigger · Condition · Action

What a flow can reach

Choose any system to see what moves between it and a flow.

Business integrations

Connect your business apps to Plexvia.

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

Website chat

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

Their message
Can I book a repair for Friday?
Channel
Web chat

Send Message replies in the chat.

Workflow builder

Build automated workflows you can see.

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.

Flows · Quote requests
FlowsQuote requestsDraft
Test with

Sam Ortiz: Hi, could you quote for repairing 12 café chairs? It’s urgent, we reopen Friday.

  1. Run a test to see each step as it happens.

A simulation. Nothing is sent, and no real system is contacted.

  • Every exit is named. Yes and No, Timed out, Error: you decide what happens on each, so nothing is left without a path.
  • Publish when it is ready. A published version keeps running while you edit the next draft.
  • Ask before acting. Collect Information asks the customer for details, one question at a time, and can keep a record of the answers.

Business process automation

Automate the work between your systems.

Four everyday jobs, each a real flow. Pick one and play it, then change what happens and watch the route change.

A quote request becomes a lead in your CRM.

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

Try

Outcome. A new lead in your CRM, and a customer who knows a quote is coming.

  1. Play it to watch each step.
Visitor asks for a quoteStart
Ask for their detailsCollect InformationWaitsNextTimed out
Add the lead to your CRMCall APIActsNextError
Confirm to the visitorSend MessageActs
Tell the sales inboxSend EmailActs
DoneEnd

A simulation. Nothing is sent, and no real system is contacted.

Automation and integrations, together

One place to connect and automate.

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.

Less repetitive work.

The details a customer gives go straight to the system that needs them. Nobody copies them across by hand.

Copy the details into the CRM
Forward the email to sales
Tell the customer someone will be in touch
Handled by one flowQuote requests

Fewer disconnected processes.

Your conversations, your team’s inboxes and the services you already pay for take part in the same flow, instead of three separate habits.

Conversations
Team inboxes
Your CRM
One flow, one set of rules

Customers hear one consistent story.

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

Replied in the chat“Thanks, Sam. Your quote is on its way.”
Sales inbox toldQuote request from Sam Ortiz
Lead added to your CRMPOST /v1/leads · 201 Created

Faster responses, every time.

A flow acts the moment it starts, and the same way each time: the same questions, the same handover, the same care.

  1. A message arrives
  2. The flow decides what it is
  3. It asks your booking system
  4. It answers, and tells the team

Room to change your mind.

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

Version 3Live
DraftBeing edited

API activity

POSTapi.your-crm.example/v1/leads201
GETapi.your-workshop.example/jobs/4471200
CRM key saved · encrypted, never shown again

Availability

Flows is part of the Plexvia private beta.

Part of the Plexvia private beta. Here is what that means for your workspace.

Part of the private beta

Flows comes with the rest of the Plexvia private beta. It is not a separate add-on.

What each plan includes

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.

Clear about what is next

Starting a flow from a webhook, on a schedule or when a record changes is planned, and marked as planned wherever it appears here.

Start with the job you repeat most.

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