FlowRunner
PricingContact
Theme
Start Free

Wayfront, formerly Service Provider Pro (SPP.co), is a client portal and operations platform for productized service agencies: orders, tasks, tickets, invoicing, a CRM pipeline and a client-facing portal. Agents create and update orders, tasks and tickets, manage clients and invoices, and keep the portal current.

61 actions API key available
Wayfront website Platform Documentation Capability data verified 2026-08-18
A retainer subscription reaches the end of its billing period
List Orders pulls the period's work with the client and service expanded in one pass
List Order Tasks confirms each order's workflow actually finished before anything gets billed
Create Invoice raises the invoice as a draft against the client
Create Order Message posts the delivery summary on the order where the client will read it
List Invoices confirms no invoice already exists for the same period
The account manager approves before Charge Invoice touches the card on file

What This Integration Enables

Wayfront is built for agencies that sell a catalog, not an estimate. The order is the unit of work, the client watches it move in their own portal, and the same account holds the tickets, the CRM pipeline, the subscriptions and the card on file. That combination is unusual, and it changes what an agent can be asked to do here: this is not a board where tasks get tidied, it is the operating record a client is billed from.

FlowRunner agents work the whole spine. They raise orders from purchases, lay out each order's task workflow, keep the client-facing conversation moving, open and answer tickets, run pipeline cards through their stages, and assemble invoices from delivered work. Because the connector reaches money as well as work, the ordinary human-in-the-loop discipline is not decoration here. The agent does the assembly at machine speed, and the charge that cannot be recalled waits for a person.

Without FlowRunner

Delivery and billing drift apart Work finishes in one place and the invoice is raised from memory in another
Portal kept current by hand Somebody has to remember to post the update the client is waiting on
Billing errors found by the client The first review of a charge happens after the client questions it

With FlowRunner

Billing follows delivery The invoice is assembled from the orders and tasks that actually completed
The portal updates itself Order messages, tickets and pipeline moves post as the work moves
The charge is reviewed before it lands A person signs off the money moving, with the delivery evidence attached

Use Case Scenarios

  • Retainer close, assembled and then approved

    At the end of a billing period the agent lists the period's orders with their client and service expanded, so it reads the whole month in one call rather than one call per order. For each order it checks List Order Tasks to confirm the workflow completed, and it separates the orders that finished from the ones still open. Create Invoice raises a draft for the finished work only. The delivery summary posts onto each order with Create Order Message so the client sees what they are being billed for before the charge arrives. Then the agent stops, posts the draft totals into Slack, and waits. Only after approval does it call Charge Invoice, or Mark Invoice Paid where the client already settled by transfer.

  • A purchase becomes a running order

    An order placed through Stripe or a storefront on Shopify reaches the agent. It matches the buyer with List Clients, calls Create Client where no match exists, and raises the order with Create Order against the purchased service. Create Order Task then lays out the delivery workflow, using the sort order as a tier so the steps that can run in parallel actually do. Generate Magic Link produces a single use sign in so the welcome email drops the client straight into their portal with no password to invent. List Form Data reads the intake answers, and where a required answer is missing the agent flags it rather than starting work on a brief that is not finished.

  • Tickets triaged against what the client actually bought

    An inbound ticket arrives. The agent reads it with Get Ticket, pulls the client's active orders and subscriptions, and decides whether the request falls inside the purchased service. In-scope requests get a reply through Create Ticket Message and a task added to the relevant order. Out-of-scope requests are the interesting case. The agent drafts the reply and the upsell and adds the client to the CRM pipeline with Add Pipeline Item, then hands the scope call to a human. One switch on that message decides whether it goes to the client or stays internal, and a commercial boundary is not something an agent should settle on its own.

Human-in-Loop Highlight

Charge Invoice is the operation that makes this connector different from every board and tracker on this site. It charges the client's card on file, immediately, and the connector publishes no reversing operation to undo it. Mark Invoice Paid records money that arrived some other way and moves nothing; Charge Invoice moves real money. So the retainer agent never calls it on its own. It posts into the finance channel: "Acme retainer, period closing. Four orders completed, one still open and excluded. Draft invoice totals 4,200 USD against the card on file. Charge now, hold for the open order, or mark paid because a transfer already landed?" A person answers, and the agent executes the answer. The same rule covers Set Subscription Status, because Wayfront has no resume from canceled: an agent that decides a client is churning gets to propose Paused, and a person decides whether it becomes Canceled.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via preferred channel
Human decides
Agent resumes with decision

Agent Capabilities

61 actions

Orders

5
  • List Orders Returns the workspace's orders. Expanding the client and service on the listing keeps a whole month readable in one call instead of one call per row.
  • Get Order Returns a single order in full. Used when a workflow already holds the identifier and needs the current state.
  • Create Order Raises an order for a client. Wayfront needs either a service or a title, because an order with no service still has to call itself something.
  • Update Order Changes an order. Assign to, tags and linked orders are replaced rather than merged, so a partial update quietly clears whatever it leaves out.
  • Delete Order Deletes an order along with its tasks and messages. Destructive, and worth a review step rather than a status change.

Order Tasks

5
  • List Order Tasks Returns the tasks on an order, which are the steps of its delivery workflow. The read behind any completion check.
  • Create Order Task Adds a step to an order's workflow. Sort order behaves as a tier rather than a position, so two tasks sharing a value both start at once.
  • Update Order Task Changes a step on an order, including its owner, description and position in the workflow.
  • Set Task Complete Marks a step complete or reopens it. One operation covers both directions because Wayfront drives them from the same route.
  • Delete Order Task Removes a step from an order's workflow.

Order Messages

3
  • List Order Messages Returns the conversation on an order, including both the client-facing messages and the internal ones.
  • Create Order Message Posts a message on an order. Leaving staff only off means the client sees it and is notified, so this single switch decides whether you are talking to the client or about them.
  • Delete Order Message Removes a message from an order.

Clients

6
  • List Clients Returns the workspace's clients. The matching step before any create, so a returning buyer does not become a second record.
  • Get Client Returns a single client record.
  • Create Client Creates a client. Wayfront stores the first and last name separately with no combined field, so a full name has to be split before it arrives.
  • Update Client Changes a client's details.
  • Delete Client Deletes a client. Their orders, invoices and tickets go with them, which is why a status change is usually the better move.
  • Generate Magic Link Returns a single use sign in link for a client, so a workflow can drop somebody straight into their portal with no password. Anyone holding the link is signed in as that client, so it is handled as a credential.

Client Activities

4
  • List Client Activities Returns a client's activity notes, including any scheduled for a future date.
  • Create Client Activity Records a note against a client, or schedules one as a follow up. Supplying a scheduled time turns the note into work for somebody rather than a record of what happened.
  • Complete Client Activity Marks a scheduled client activity as done.
  • Delete Client Activity Removes an activity note from a client.

Client Portal Links

3
  • List Client Links Returns the custom sidebar links shown to one client inside their portal.
  • Create Client Link Adds a custom link to one client's portal sidebar. The icon is required and has to be a name the workspace recognizes.
  • Delete Client Link Removes a custom sidebar link from a client's portal.

Tickets

5
  • List Tickets Returns the workspace's helpdesk tickets. The read behind triage and backlog reporting.
  • Get Ticket Returns a single ticket.
  • Create Ticket Opens a helpdesk ticket for a client. Supplying the first message posts it on the new ticket in the same call, which removes a second request and the race that comes with it.
  • Update Ticket Changes a ticket. Assign to and tags are replaced rather than merged.
  • Delete Ticket Deletes a ticket and its conversation.

Ticket Messages

3
  • List Ticket Messages Returns the conversation on a ticket.
  • Create Ticket Message Replies on a ticket. As with order messages, leaving staff only off sends the reply to the client and notifies them.
  • Delete Ticket Message Removes a message from a ticket.

Invoices

6
  • List Invoices Returns the workspace's invoices. Used to check for a duplicate before raising a new one.
  • Get Invoice Returns one invoice with its line items, which is what a review step reads before approval.
  • Create Invoice Raises an invoice. A draft is a real state here rather than an absence of one, so drafting and charging are genuinely separate steps.
  • Charge Invoice Charges the client's card on file. This moves real money immediately and the connector offers nothing to reverse it, which is why it is the gated operation on this page.
  • Mark Invoice Paid Records an invoice as settled without taking any money. The right call when the client paid by transfer or in cash.
  • Delete Invoice Deletes an invoice.

Subscriptions

2
  • List Subscriptions Returns the workspace's recurring subscriptions, which is where retainer revenue lives.
  • Set Subscription Status Pauses, resumes or cancels a subscription. Canceling stops the billing permanently and there is no resume from canceled, so paused is the reversible option.

Services and Catalog

6
  • List Services Returns the services the workspace sells, which is the catalog an order is raised against.
  • Get Service Returns one service with its pricing.
  • Create Service Creates a service the workspace can sell.
  • Update Service Changes a service. Changing a price does not reprice orders already placed at the old one.
  • Delete Service Removes a service from the catalog. Orders already placed against it are untouched.
  • List Coupons Returns the workspace's discount coupons.

CRM Pipelines

6
  • List Pipelines Returns the CRM pipelines the connection can see, with their stages.
  • Get Pipeline Returns one pipeline with its stages, which is where the stage identifiers a move needs come from.
  • List Pipeline Items Returns the cards standing in a pipeline.
  • Add Pipeline Item Puts a client onto a pipeline. The step that turns an out-of-scope ticket into a tracked opportunity.
  • Move Pipeline Item Moves a card to another stage. Sort order is a zero-based position inside the target stage rather than a relative nudge.
  • Remove Pipeline Item Takes a card off a pipeline. The client record itself is untouched.

Team and Reference

5
  • List Team Returns the workspace's team members, who are who an order or a ticket can be assigned to.
  • Get Team Member Returns one team member.
  • List Tags Returns the tags orders and tickets can carry.
  • List Icons Returns the icon names a client sidebar link will accept, which is the only reliable way to know what Create Client Link can use.
  • List Logs Returns the workspace activity log, which is how a workflow audits what changed and who changed it.

Forms

2
  • List Form Data Returns filled form fields, which is where the answers a client gave on an intake form live.
  • Update Form Field Changes the answer stored in one filled form field, so a workflow can correct or enrich what a client submitted.

Frequently Asked Questions

What can FlowRunner do with Wayfront?

FlowRunner agents can run List Orders, Get Order, and Create Order in Wayfront, plus 58 more actions.

Does connecting Wayfront to FlowRunner require OAuth?

No. Wayfront connects to FlowRunner with an API key, no OAuth flow required.

Can Wayfront trigger a FlowRunner workflow automatically?

Wayfront doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Wayfront

Free plan, no card required. Connect in minutes.