VBOUT
Email MarketingSync ecommerce activity and read marketing data with the VBOUT API, covering carts, orders, and transactions. Agents trigger recovery and lifecycle campaigns off what shoppers actually did.
What This Integration Enables
VBOUT's connector is shaped around ecommerce, and that shape is deliberate. What an agent pushes here is behaviour: carts and the items in them, completed orders with tax, discount and shipping broken out separately, individual payment transactions including the failures, and browse intent from product searches, product views and category views. VBOUT's own journeys do the recovering. The integration's job is to make sure they are reacting to what actually happened rather than to a file that was accurate yesterday.
One thing this page will not claim: full email marketing management. VBOUT documents contact, list and campaign writes only inside a key-gated Swagger console, so those field schemas are not public. Rather than guess at them and ship an operation that silently writes the wrong shape, the connector leaves them out and exposes the email marketing surface as read-only: lists, contacts, campaigns and forms can be read, and writes go through the ecommerce and customer operations. That is a smaller surface honestly described, which is worth more to a workflow than a larger one that fails at runtime. Every connector FlowRunner ships is built and verified against the vendor's official API, and where the vendor does not publish an API, we say so.
Without FlowRunner
With FlowRunner
Use Case Scenarios
The first sync, which is the one that goes wrong
A store connecting VBOUT for the first time has years of orders and a pile of baskets that were open when the export ran. Loading them naively tells VBOUT that thousands of shoppers just abandoned a cart. The agent handles the two halves differently: Create Order syncs completed purchases first, which closes out the carts they came from, and the still-open baskets are held back until someone confirms the recovery journeys are paused. Ecommerce tracking also has to be enabled for the domain in VBOUT before any of the cart, order or intent operations will attach to it, so the agent checks that the Ecommerce Domain Key resolves before it starts rather than discovering it halfway through a load.
The live basket, item by item
Once the store is running, an agent posts each event as the shopper produces it. Create Cart opens the basket, Add Cart Item posts one product line per call with pricing, quantity, category and imagery so the recovery email can render a real product block, and Remove Cart Item takes a line back out when the shopper does. Because shoppers are matched by email first, then unique shopper ID, then IP address, the agent passes the email the moment checkout captures it, and the anonymous session's earlier activity merges into the named profile. Alongside the basket, Add Product View, Add Product Search and Add Category View record what the shopper considered and did not take, which is the intent data recommendation blocks are built from. When the shopper clears their basket by hand, Empty Cart keeps the cart record and stops abandonment firing, which is a different thing from the basket being abandoned.
Payment failures as a marketing event
An order in Shopify or WooCommerce completes and Create Order syncs it with its totals, taxes, discounts and shipping recorded separately so attribution runs on net figures. Then Create Order Transaction logs each payment attempt against it, including the declines and the refunds, not just the successful charge. That is what lets a dunning journey exist at all: without the failed attempt, a card that did not go through is indistinguishable from a shopper who never tried. Refunds and fulfilment progress reach the same journeys through Update Order, matched on the order ID the store already assigned.
Human-in-Loop Highlight
A cart in VBOUT is not a record, it is the start of a timer. Create Cart followed by Add Cart Item tells VBOUT a shopper has an open basket, and if a recovery journey is live, the messages that journey sends are real messages to real customers. So a data migration or a replay after an outage is the dangerous operation here, not a delete: loading ten thousand historical baskets can enrol ten thousand people in an abandonment sequence for items they bought last spring or that no longer exist. Unwinding it is worse than causing it, because Remove Cart deletes one cart at a time and the connector exposes no batched form of it, so the cleanup is ten thousand calls behind ten thousand messages already sent.
The agent therefore treats the first load, and any replay, as a decision rather than a task. It reads Get Campaigns and Get Forms, counts the still-open baskets in the export, and stops with the digital andon cord pulled: "Historical sync ready. 41,200 completed orders will load safely because each one closes its own cart. 3,860 baskets were open at export time and 2 abandonment journeys are currently live, so those baskets would enter them. Undo is one Remove Cart call per basket. Pause the journeys and load, load orders only and hold the baskets, or abort?" An ecommerce owner answers, the human-in-the-loop step returns the choice, and the load runs the way a person chose. The agent is fully capable of pushing all 45,000 rows. Knowing which of them are safe to push is the part it hands over.
Agent Capabilities
21 actionsCarts
6- Create Cart Opens a shopping cart in VBOUT for a shopper so later item additions, abandonment reminders and order syncing all attach to the same basket. Shoppers are matched by email first, then unique shopper ID, then IP address, so passing an email as soon as checkout captures one is what keeps activity attached to a person.
- Update Cart Refreshes a cart's metadata, such as the shopper's email once checkout captures it or a new abandonment return link. The items are untouched, which is what makes it safe to call repeatedly as a session develops.
- Empty Cart Clears every item from a cart while keeping the cart record. This is the correct call when a shopper manually empties their basket, because abandonment automations stop firing without the cart's history being destroyed.
- Remove Cart Deletes a cart and all of its items. Used when a basket was created in error or a shopper's data must be purged, and it operates on one cart per call, which is why a bulk cleanup is expensive.
- Add Cart Item Adds one product line to a cart with pricing, quantity, category and imagery so abandonment emails can render a real product block. Send one call per product, and include the variation object when a single product ID covers several options.
- Remove Cart Item Removes one product line from a cart and leaves the rest in place. Pass the same variation object used when the item was added so the right option is targeted where one product ID covers several variants.
Orders
3- Create Order Syncs a completed purchase into VBOUT, closing out the cart it came from and unlocking revenue reporting, post-purchase journeys and lifetime value segmentation. Totals, taxes, discounts and shipping are recorded separately so attribution can work on net figures.
- Update Order Updates an order already in VBOUT, which is how fulfilment progress, refunds and corrected totals reach post-purchase journeys. Matched on the order ID sent at creation, so the store's own identifier stays authoritative.
- Create Order Transaction Records one payment attempt against an order, covering initial charges, refunds and subscription rebills. Logging failures as well as successes is what gives dunning and payment recovery journeys something to react to.
Intent
3- Add Product Search Records a shopper's on-site search term as intent data feeding recommendation and re-engagement journeys. Send the email whenever it is known so the search attaches to a profile instead of an anonymous session.
- Add Product View Records a product page view with full product context so browse abandonment emails can render the item the shopper looked at. The same identity rule applies: an email turns a session into a person.
- Add Category View Records a category page view, which is how VBOUT learns which departments a shopper browses without buying. Category interest then drives preference-based segments and recommendation blocks.
Customers
2- Upsert Customer Adds a shopper to the ecommerce contact list, or updates them if they exist. Used to push newly registered customers ahead of any purchase so a welcome journey can start before the first order rather than after it.
- Update Customer Preferences Replaces the set of product categories a customer has declared an interest in. It overwrites rather than merges, so a workflow always sends the complete set, and reading the current set before writing is not optional.
Email Marketing
7- Get Lists Returns every email marketing list in the account with its identifiers and names. The first call when wiring an integration, to resolve a list name into the ID contact operations expect.
- Get List Retrieves one list by identifier with its settings. Used to confirm a list still exists before a workflow syncs contacts toward it.
- Get Contacts Returns the contacts belonging to a given list. Used to export an audience, reconcile subscribers against a CRM, or drive a downstream enrichment step.
- Get Contact Retrieves one contact by VBOUT identifier with its stored profile fields. The follow-up call after a lookup by email when the full record is needed rather than a match.
- Find Contact By Email Looks a contact up by address within a specific list, which is the standard way to check whether someone is already subscribed before adding them.
- Get Campaigns Returns the email campaigns in the account with identifiers and names. Used to discover which journeys are live before a bulk load, and to confirm a campaign exists before referencing it.
- Get Forms Returns the signup forms defined in the account. Used to map a form identifier to its name so incoming leads are attributed to the capture point that produced them.
Frequently Asked Questions
What can FlowRunner do with VBOUT?
FlowRunner agents can run Create Cart, Update Cart, and Empty Cart in VBOUT, plus 18 more actions.
Does connecting VBOUT to FlowRunner require OAuth?
No. VBOUT connects to FlowRunner with an API key, no OAuth flow required.
Can VBOUT trigger a FlowRunner workflow automatically?
VBOUT doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with VBOUT
$100 in credits. No card required. Connect in minutes.