FlowRunner
PricingContact
Theme
Start Free

Custify

CRM

Connect AI agents to Custify, the customer success platform. Agents sync people and companies, track product events, keep subscription and revenue data current, log NPS responses, and manage customer success tasks to power health scores and playbooks.

18 actions API key available
Custify website ↗ Platform Documentation ↗ Capability data verified 2026-07-27
A detractor score arrives from the NPS survey tool
Create NPS Response logs the score and the written feedback on the person, tied to their company
Get Company pulls the account's plan, revenue, and custom attributes
The account's ARR and renewal window set the escalation level
The CSM reads the verbatim and the account context and decides whether this is a save play or a routine follow-up
Create Task books the chosen play on the CSM's list with a due date and description
Track Event records the escalation decision on the customer timeline
The CS channel gets the score, the quote, and the owner

What This Integration Enables

A customer success platform is a derivative instrument: health scores, segments, and playbooks are computed from whatever data reaches it, and most CS teams feed it manually. This connector makes the feed continuous. FlowRunner agents upsert people and companies by identifier so repeated syncs keep single records, track product events onto customer timelines, sync subscriptions from the billing system so MRR and renewal metrics stay honest, import NPS responses collected anywhere, and create and update the tasks that turn signals into CSM work. The upsert semantics are the quiet advantage: Create or Update Person matches on user_id then email, and Create or Update Company matches on your company_id, so agents can sync aggressively without ever manufacturing duplicates. The judgment calls, which detractor gets the save play, whose data gets erased, stay with people through FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) gates.

Without FlowRunner

Health scores fed by stale data Usage, revenue, and survey results arrive in Custify by periodic CSV, if at all
Billing and CS disagree The CSM prepares a renewal against MRR numbers the billing system stopped agreeing with weeks ago
Detractors discovered late The angry survey response surfaces at the QBR, after the renewal conversation went badly

With FlowRunner

The feed is continuous Users, accounts, events, subscriptions, and NPS flow in as they happen, upserted by identifier
One revenue truth Subscription changes sync from billing the day they occur, so renewal metrics hold
Detractors trigger plays A bad score becomes a task on the right CSM's list the same hour, with context attached

Use Case Scenarios

The account record that mirrors billing

When a subscription changes in [Stripe](/integrations/stripe), the agent calls Create or Update Company for the account and Create or Update Subscription with the new plan, pricing, and billing dates. Downgrades fire Track Event onto the timeline so the health score sees the contraction the day it happens. When the CSM opens the account before a renewal call, the revenue picture is the billing system's, not a quarter-old copy.

Product usage on the timeline, not in a warehouse

Signups flow from the app: Create or Update Person onboards each user with their company attached, and Track Event logs activations, feature usage, and the milestones the CS playbooks key on. A [HubSpot](/integrations/hubspot) enrichment pass fills in title and company size so sales and CS read the same profile. Segments and health scores run on live behavior, and the first-value milestone triggers the onboarding check-in task automatically.

NPS from anywhere, closed-loop by default

Survey responses collected in any tool land through Create NPS Response with score and verbatim. Detractors follow the escalation flow on this page; promoters generate a Create Task for the advocacy ask at the right moment. Quarterly, List NPS Responses exports the full set with promoter and detractor categories to the reporting sheet, and List Tasks reconciles which follow-ups actually happened. The survey stops being a score and becomes a queue.

Human-in-Loop Highlight

Delete Person and Delete Company are permanent: the record is removed and cannot be undone, and with it goes the timeline, the health history, and the context the CS team accumulated over the relationship. These operations exist for a reason, data-removal requests under privacy law and test-data cleanup, and both are exactly where an agent should stop. When a deletion request arrives, the agent does the assembly: locates the person with Get Person, maps their company link, and lays out what will be erased. The privacy owner confirms the identity match is right and the request is genuine, and only then do the deletes run. An over-eager match here does not send a wrong email; it erases a real customer's history while the actual requester's data survives. That asymmetry is why the confirmation is a human's.

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

Agent Capabilities

18 actions

People

5
  • Create or Update Person Upserts an end user matched on user_id then email, with company attachment and custom attributes. The default write for user syncs.
  • Get Person Retrieves a person by Custify ID or your user_id with their full profile and attributes.
  • List People Pages through the workspace's people for exports and reconciliation sweeps.
  • Update Person Changes only the fields you supply on an existing person, leaving other attributes intact.
  • Delete Person Permanently deletes a person. The data-removal operation this page's human gate exists for.

Companies

5
  • Create or Update Company Upserts an account matched on your company_id, carrying plan, size, revenue, and custom attributes. The account-sync workhorse.
  • Get Company Retrieves an account by Custify ID or company_id with its full record. The context read behind escalation decisions.
  • List Companies Pages through accounts for portfolio sweeps and exports.
  • Update Company Changes only the supplied fields on an existing account.
  • Delete Company Permanently deletes an account record. Cannot be undone; runs only with review.

Events

1
  • Track Event Records a custom event on a person's timeline, optionally scoped to a company, with metadata and backfill timestamps. The fuel for health scores, segments, and playbooks.

Subscriptions

2
  • Create or Update Subscription Upserts a company's subscription with plan, pricing, and billing dates, keyed on your subscription_id. The step that keeps MRR and renewal metrics current.
  • Delete Subscription Removes a subscription when billing removes it, so revenue metrics do not count ghosts.

NPS

2
  • Create NPS Response Records a 0 to 10 score with written feedback for a person, optionally tied to a company. The import path for surveys run anywhere.
  • List NPS Responses Pages through recorded responses with scores, categories, and feedback for trend analysis and export.

Tasks

3
  • Create Task Creates a CS task linked to a company or person, assigned to a CSM with a due date. How signals become work.
  • Update Task Reschedules, reassigns, edits, or completes an existing task.
  • List Tasks Pages through tasks, optionally filtered by company, for workload review and reconciliation.

Frequently Asked Questions

What can FlowRunner do with Custify?

FlowRunner agents can run Create or Update Person, Get Person, and List People in Custify, plus 15 more actions.

Does connecting Custify to FlowRunner require OAuth?

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

Can Custify trigger a FlowRunner workflow automatically?

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

Start building with Custify

$100 in credits. No card required. Connect in minutes.