Authvia

Authvia is a text-to-pay platform that collects payments through conversational messaging. Agents manage customers and their payment methods, launch business processes and blueprints, create transactions and bulk jobs, and act on webhook events in real time.

1 trigger 52 actions Custom auth available

Authvia website Platform Documentation Capability data verified 2026-08-25

An invoice passes its due date in the accounting system

Agent reads the customer, the balance, and the mobile number on file

List Account Products confirms a messaging and a payments provider are configured

Execute Blueprint starts the collection conversation for that one customer

Get Business Process reads the ordered actions and where the customer stopped

The result posts to the collections channel with the transaction state

The collections lead approves the batch before the same conversation goes to a list

What This Integration Enables

Authvia's premise is that the payment is the conversation. A business process is a text message exchange with a customer that collects a payment, a signature, an approval, an acknowledgement, or a document, and its actions are the ordered steps the customer actually experiences. Change the order and you have changed the product, not the configuration. Blueprints are the reusable templates for those conversations, and a blueprint's name is literally its identifier, which is a good indication of how central they are.

FlowRunner agents run that surface end to end. They create customers keyed on your own reference rather than a vendor id, attach payment methods, execute a blueprint against one customer or a whole file, read the resulting business process action by action, and take, hold, refund, or reverse money through the transaction routes. Because the output of every conversation is a message a real person receives, human-in-the-loop sits in front of the volume rather than after it.

Without FlowRunner

Collections by phone tag Getting paid depends on reaching someone who is not expecting the call

Payment friction at the end The customer agrees to pay, then has to find a portal, a login, and a card

Conversation state is invisible Nobody can say which customers replied, stalled, or never saw the message

With FlowRunner

The ask arrives where they answer The request and the payment happen in the same message thread

Payment is one reply away The conversation collects the method and takes the payment inside itself

Every step is readable The ordered actions on a business process say exactly where each customer stopped

Use Case Scenarios

One overdue invoice, one conversation

An invoice goes past due in NetSuite. The agent resolves the customer by the reference your own systems already use, checks with List Account Products that a messaging provider and a payments provider are both configured, and calls Execute Blueprint with the invoice number and amount as variables. Authvia texts the customer, collects a payment method if there is none on file, and takes the payment. The agent reads the outcome with Get Business Process and List Actions, then writes the payment back and posts the result to Slack. Nothing about this requires the customer to find a portal.
Authorizations that were never captured

Money that was held and never taken is invisible in most reporting because the charge looks like it happened. On a schedule, the agent calls List Transactions filtered to authorizations, then Get Transaction on each one to read its child transactions and see how much of the hold is still standing. Anything past its useful life is either captured with Create Child Transaction or released. The summary lands in the reconciliation sheet in Google Sheets next to the aged receivables extract, so the finance team is looking at held money and owed money on the same page.
A conversation that stalled halfway

Not every customer finishes. The agent lists business processes that have not resolved, reads the ordered actions on each, and separates the customer who never received the message from the one who read it and stopped at the payment step. The first case is a delivery problem and routes to an address check with Replace Customer Addresses, because the first address on the record is the number the conversation goes to. The second is a collections problem and becomes a task for a person in HubSpot. Two different failures that look identical in a payment report get separated before anyone chases the wrong one.

Human-in-Loop Highlight

Create Bulk Transaction and Create Account Job are how a single decision reaches a whole file of customers at once, and a text message asking somebody for money cannot be recalled. The single-process route has a guard: Create Business Process takes a seed value that makes the call idempotent, so a retried workflow is refused rather than texting the customer twice. The bulk path does not carry that guard, and running a process asynchronously returns no body at all, which means the agent does not even hold the identifiers of the conversations it just started. So the batch is where the agent stops. It runs the blueprint against one named account first, then posts: "Blueprint late-invoice-v3 ran against Rivera Plumbing. The message sent at 09:14, they added a card, and transaction 4C2 captured $842. The queued run covers 318 customers with a combined balance of $214,000, sending to the first address on each record. Release the batch, or review the address list first?" The collections lead answers once. The 318 conversations that follow are the agent's work, and the decision to start them belongs to a person who will hear about it if the list was wrong.

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

52 actions

Account

Get Account Reads the Authvia account the connection acts on, including its configuration.
Update Account Updates account level settings.

Products

List Account Products Lists the configured capabilities: the payments provider, the messaging provider, the tokenization provider. This is the first thing to read when a conversation fails for no visible reason, because a payment step cannot work without a payments product.
Create Account Product Adds a capability to the account. A newly created product goes to the bottom of the list, and the bottom of a conflicting set is the one Authvia prefers.
Get Account Product Reads one configured product.
Update Account Product Updates a product's configuration.
Delete Account Product Removes a product from the account, which disables whatever conversations depended on it.

Customers

Create Customer Creates a customer addressed by your own reference rather than a vendor id, so the record joins cleanly to whatever system already owns the relationship.
List Customers Lists customers with paging. Application data is not returned here, only on single reads and webhook payloads.
Get Customer Reads one customer in full, including their application data.
Update Customer Merges changes into a customer. Only supplied fields change.
Replace Customer Replaces a customer wholesale. Anything omitted is lost, which is the difference between this and Update Customer.
Delete Customer Removes a customer along with their payment methods, transactions, and business processes, permanently. There is no soft delete.
Create Customer Address Adds an address to a customer. Adding one does not make it the default.
List Customer Addresses Lists a customer's addresses in order. The first entry is the default, which on a text-to-pay platform is the number conversations go to.
Replace Customer Addresses Replaces the ordered address list, which is how the default is actually changed.

Payment Methods

Create Payment Method Stores a payment method against a customer for later charges.
List Payment Methods Lists a customer's stored payment methods.

Transactions

Create Transaction Creates a transaction whose action decides whether money moves: charge takes it, authorize only holds it, payout sends it to the customer, reversal undoes an earlier one, and none records without processing anything.
Create Child Transaction Captures, refunds, voids, or reverses against a parent transaction, optionally for part of the amount.
List Transactions Lists transactions with filters. Filtered to authorizations, this finds holds that were never captured, which is money not actually collected.
Get Transaction Reads one transaction with its child transactions, which is what says how much of a charge is still standing.
Create Bulk Transaction Creates transactions across many customers in one call. The route this page's human gate sits in front of.

Business Processes

Create Business Process Starts a conversation with a customer. It takes a seed value that makes the call idempotent, so a retried workflow is refused rather than texting the customer a second time.
List Business Processes Lists conversations and their states, which is how stalled ones are found.
Get Business Process Reads one conversation in full.
Update Business Process Updates a conversation in flight.
List Actions Lists a conversation's ordered steps. The order is the customer's experience, so this is how you see exactly where somebody stopped.
Get Action Reads one step of a conversation and its outcome.

Blueprints

Create Blueprint Creates a reusable conversation template with its dynamic variables. The name becomes the identifier, so it must be unique and renaming is not cosmetic.
List Blueprints Lists the account's blueprints.
Get Blueprint Reads one blueprint and its variables.
Execute Blueprint Runs a blueprint for one customer with just the variables filled in. The everyday route for starting a conversation.
Delete Blueprint Removes a blueprint from the account.
Create Blueprint Trigger Attaches a trigger to a blueprint, one per protocol and resource pair.
List Blueprint Triggers Lists the triggers attached to a blueprint.
Get Blueprint Trigger Reads one blueprint trigger.
Delete Blueprint Trigger Removes a trigger from a blueprint.

Jobs

Create Account Job Submits a batch job against the account. The bulk path, and the one without the per-call idempotency guard the single-process route has.
List Account Jobs Lists jobs from the last thirty days, optionally as CSV. Built for polling.
Get Account Job Lines Reads a job's individual lines. A partially failed batch reports only that it failed, and this is where you learn which records did.

Files

Get Upload URL Returns a presigned URL and metadata. The workflow then puts the bytes to it, which makes an upload two steps rather than one.
Get Download URL Returns a presigned URL for reading a stored file back.
List Files Lists stored files.
Update File Metadata Updates a file's metadata. The bytes cannot be changed, so a corrected file means delete and re-upload.
Delete File Removes a stored file. Deleting one an active conversation references breaks that conversation.

Webhooks

Create Webhook Subscription Registers a subscription. Each one carries exactly one event type, with no wildcard.
List Webhook Subscriptions Lists subscriptions and their states. Authvia disables a subscription that keeps failing, so this is where a trigger that went quiet is diagnosed.
Get Webhook Subscription Reads one subscription.
Update Webhook Subscription Changes only whether a subscription is disabled, which is how a disabled one is revived. Event type, destination, and secret are fixed.
Delete Webhook Subscription Removes a subscription.
List Subscription Events Lists deliveries, including the ones sent while an endpoint was down. The replay path.

Triggers

1 triggers

Event Triggers

On Authvia Event Fires on Authvia's webhook events, with a business process update usually being the one worth subscribing to, because that is what fires when a conversation resolves. Authvia allows one event type per subscription and no wildcard, so an all-events trigger registers each subscription separately and removes them together on teardown. Deliveries are verified against the account's shared secret when one is set on the connection.

Frequently Asked Questions

What can FlowRunner do with Authvia?

FlowRunner agents can run Get Account, Update Account, and Create Account Product in Authvia, plus 49 more actions.

Does connecting Authvia to FlowRunner require OAuth?

Authvia uses a custom authentication method to connect to FlowRunner.

Can Authvia trigger a FlowRunner workflow automatically?

Yes. Authvia supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with Authvia

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us