Outseta
CRMConnect AI agents to Outseta, an all-in-one membership platform combining CRM, billing, and support. Agents create people, accounts, and deals, add payments to invoices, open and reply to support cases, and read the subscriptions behind each account.
What This Integration Enables
Outseta's whole product decision is that CRM, subscription billing, email, and the help desk are one database rather than four tools stitched together, and that is exactly what makes it worth automating. In a stack where billing and CRM are separate products, an agent has to reconcile two identities before it can reason about a member at all. Here a person, the account they belong to, the subscription that bills that account, the invoices under it, the email lists they are on, and the support cases they opened are all reachable from the same connection. FlowRunner agents work that whole model: create, update, and delete people, accounts, and deals; add and remove people from accounts; cancel accounts and extend trials; read subscriptions, plans, invoices, and transactions; add a payment against an invoice; subscribe and unsubscribe members from email lists; open support cases and post agent replies; and record custom activity events.
Two mechanics shape how flows are built against it. Create and update actions for people, accounts, and deals expose the common fields as parameters plus an Additional Fields object merged into the request body verbatim, so field names have to match Outseta's PascalCase schema exactly. And Record Custom Activity is not passive logging: setting the Title to match a drip campaign's configured start or stop value is how you start or stop that campaign, which means a string in an activity payload can begin an email sequence to a real member. On events, be clear about what this connector does and does not do. It exposes no triggers. Outseta configures webhook subscriptions in its admin console rather than through the REST API, and the API publishes no webhook subscription endpoint, so nothing in Outseta starts a FlowRunner flow. Change detection runs by polling Get Activities with an ActivityDateTime filter and a set of numeric activity type codes, which is honest and works, and is a different thing from receiving an event. The connector is built and verified against Outseta's official API.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Signup Landing in the Right Account
A signup arrives from a marketing site or a partner form. The agent calls Get People to check whether the email already exists, and Get Accounts to check whether the company domain is already a customer. If the person is new but the account is not, it calls Create Person and then Add Person to Account rather than creating a second organization with one seat in it. It calls Subscribe Person to Email List for the onboarding sequence and Record Custom Activity with a Title matching the onboarding drip's start value. The result is one account with the right people under it, instead of the slow accumulation of duplicate organizations that makes a membership database stop being useful in the second year.
Pipeline That Reflects Billing Reality
A sales flow keeps deals in step with what is actually being paid. When a trial account converts, the agent reads Get Subscriptions and Get Plans to see which plan was chosen, calls Update Deal to move the deal to the matching stage with the correct value, and posts the outcome to a Slack channel. When a trial lapses without conversion, it reads Get Activities to see whether the member ever logged in, and either calls Extend Trial for accounts showing genuine usage or moves the deal to a closed stage. The pipeline stops being a set of stale guesses about accounts that already decided.
Support Cases That Start With Context
A member replies to a billing email or files a form elsewhere. The agent calls Get Person and Get Account to resolve who they are, Get Invoices and Get Transactions to pull the billing history, and Get Knowledge Base Articles to find the article that matches the question. It calls Create Support Case with the history attached and Add Agent Reply to Case with a draft response and the article link. A support person opens a case that already contains the answer and the evidence, and either sends the reply or rewrites it. The agent has done the assembly; the words that reach the customer are still chosen by a person.
Human-in-Loop Highlight
Cancel Account is where this connector stops being a data integration and starts being a business decision. An automated dunning flow can read an unpaid invoice, see a failed transaction, and end a paying relationship on the strength of a card that expired, and Outseta's own documentation is clear that Cancel Account schedules a subscription cancellation while Delete Account is permanent and cannot be undone. A member who lost a card is indistinguishable, in the invoice data alone, from a member who left. So the agent builds the case and stops. It reads Get Invoices for the balance and its age, Get Transactions for whether earlier payments ever succeeded, Get Subscription for the plan and lifecycle stage, and Get Activities for whether this person has logged in or opened a support case in the last month, then posts to the account owner: "Account [name] has an unpaid balance of [amount], [n] days past due on the [plan] plan. Prior payments: [history]. Last activity: [date and type]. Cancel Account, Extend Trial, or open a support case and reach out?" The owner picks, and the agent executes the choice against the same connection. The same discipline covers Record Custom Activity, because a Title that matches a drip campaign's start value launches an email sequence to that member the moment it is written. Reading billing data needs no human. Ending a membership, or starting a campaign at one, is human-in-the-loop work.
Agent Capabilities
37 actionsPeople
5- Get People Returns a paginated list of people in the account, with the standard list envelope of metadata and items. Used to check whether a signup already exists before creating a duplicate.
- Get Person Retrieves a single person by their Uid. Used to pull the full record before an update or before drafting a support reply.
- Create Person Creates a new person record, with common fields as parameters plus an Additional Fields object merged into the request body. Used when a signup arrives from a form, a partner, or another system.
- Update Person Modifies fields on an existing person. Used to keep contact details, custom fields, and preferences in step with the source of truth elsewhere in the stack.
- Delete Person Permanently removes a person record. This cannot be undone, so it belongs behind a review step rather than inside an unattended cleanup job.
Accounts
9- Get Accounts Returns a paginated list of accounts. Used to resolve whether a company domain is already a customer before creating a second organization for it.
- Get Account Retrieves a single account by Uid, including its stage. Used before any lifecycle change.
- Create Account Creates a new account, with common fields plus an Additional Fields object. Used when a genuinely new organization signs up.
- Update Account Modifies an existing account, including moving it between stages. Used to keep the account record aligned with billing and usage reality.
- Delete Account Permanently removes an account record. This cannot be undone.
- Add Person to Account Links an existing person to an account with a membership role. Used to put a new seat under the organization that already exists instead of creating a duplicate.
- Remove Person from Account Unlinks a person from an account. Used in offboarding flows when someone leaves a customer organization.
- Cancel Account Schedules a subscription cancellation for the account. This ends a paying relationship, so it is the operation this connector puts behind a human decision.
- Extend Trial Extends the trial period on an account. Used when usage data shows a member is genuinely evaluating and simply ran out of runway.
Deals
5- Get Deals Returns the deals in the pipeline. Used for reporting and for reconciling pipeline against billing.
- Get Deal Retrieves a single deal by Uid.
- Create Deal Creates a new deal, with common fields plus an Additional Fields object. Used when an inbound signup or a qualified lead should enter the sales pipeline.
- Update Deal Modifies an existing deal, including its stage and value. Used to move a deal when a subscription actually starts rather than when someone remembers to.
- Delete Deal Permanently removes a deal. This cannot be undone.
Billing
7- Get Subscriptions Returns subscriptions with their lifecycle state. Used to see what an account is actually paying for before making a decision about it.
- Get Subscription Retrieves a single subscription by Uid.
- Get Plans Returns the plans configured in the account. Used to map a subscription to the plan name and price a human will recognize.
- Get Invoices Returns invoices with their balances. Used as the starting point of dunning and revenue reporting flows.
- Get Invoice Retrieves a single invoice by Uid, including its line items.
- Add Payment to Invoice Records a payment against an invoice. Used to reconcile a payment that was collected outside Outseta so the member's balance reflects it.
- Get Transactions Returns the transaction history. Used to tell a card that just expired apart from an account that never paid.
Email Lists
3- Get Email List Subscribers Returns the people subscribed to an email list. Used to check current membership before adding or removing anyone.
- Subscribe Person to Email List Adds a person to an email list. Used in onboarding flows to place a new member on the right sequence.
- Remove Email List Subscriber Removes a person from an email list. Used in offboarding and in preference management flows.
Support
6- Get Support Cases Returns support cases. Used to check whether a member has an open issue before a billing flow takes action on their account.
- Get Support Case Retrieves a single support case with its history.
- Create Support Case Opens a new support case, with a case source. Used to turn an inbound message from another tool into a tracked case with billing context already attached.
- Add Agent Reply to Case Posts an agent reply on an existing case. Used to draft a response for a human to approve, or to post a confirmed answer once one is approved.
- Get Knowledge Base Articles Returns knowledge base articles. Used to find the published answer that matches an incoming question.
- Get Knowledge Base Article Retrieves a single knowledge base article, including its content, for inclusion in a reply.
Activity
2- Record Custom Activity Records a custom activity against an account, person, or deal, with a Title and the target entity Uid. Setting the Title to match a drip campaign's configured start or stop value starts or stops that campaign, so this action can begin an email sequence to a real member.
- Get Activities Returns activity events, filtered by one or more numeric activity type codes and limited to the last year unless an ActivityDateTime filter is supplied. This is the polling surface used for change detection, since the connector exposes no triggers.
Frequently Asked Questions
What can FlowRunner do with Outseta?
FlowRunner agents can run Get People, Get Person, and Create Person in Outseta, plus 34 more actions.
Does connecting Outseta to FlowRunner require OAuth?
Outseta uses a custom authentication method to connect to FlowRunner.
Can Outseta trigger a FlowRunner workflow automatically?
Outseta doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Outseta
$100 in credits. No card required. Connect in minutes.