SALES
Adaptive Multi-Channel Conversion Agent
An agent that continuously reviews each trial's usage trajectory in Postgres, decides the best next conversion action and channel per account, and orchestrates email.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled agent cycle
- ActionPull usage trajectory and prior touchesPostgres
- LogicAgent chooses next action and channel
- ActionSend tailored nurture emailGmail
- ActionAlert rep and update deal for high-intentHubSpot
- OutputPost rep Slack alertSlack
- ActionRecord decision and rationalePostgres
What it does
Runs an agent over each trial account's usage history and decides, per account, the single best next conversion move and channel, then executes it: a nurture email, a rep Slack alert, or a HubSpot deal update, adapting as behavior changes.
When to use it
Use this when fixed-threshold rules aren't enough and you want judgment over the conversion path, blending PLG self-serve nudges with sales-assist for higher-intent accounts. Best for teams running both motions at once.
How it works
- 1A schedule wakes the agent on a regular cadence.
- 2The agent pulls each active trial's usage trajectory and prior touches from Postgres.
- 3It reasons over momentum, stage, and intent to choose one next action and channel per account.
- 4For self-serve accounts it sends a tailored Gmail nudge; for high-intent accounts it posts a Slack alert to the rep and updates the HubSpot deal stage and notes.
- 5The agent records its decision and rationale to Postgres so the next cycle builds on it rather than repeating.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect GmailRead, draft, send, label.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Connect HubSpotCRM, deals, marketing, support.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Sales workflows
API-Usage Surge PQL Router
When an account's API call volume surges past a rolling baseline in the product DB, it qualifies the account as a product-qualified expansion lead.
Seat-Limit Approaching Upsell Alert
Fires the moment an account's active-seat count crosses 90% of its contracted limit in the product database.
Enrich new MAP steps with Salesforce deal context on creation
When a new card is added to the mutual action plan Trello board, it looks up the linked Salesforce opportunity and writes deal owner, amount, and close date onto the card…
Power-Feature Adoption Expansion Digest
Each Monday, finds accounts that started heavily using a premium or add-on feature in BigQuery, ranks them by expansion potential.
Send buyers a weekly mutual action plan health recap
Each week it reads the MAP Trello board, computes completed, on-track, and overdue steps, and emails the buyer champion a clean recap of progress and what is due next.
Escalate to the deal team when the buyer side of a MAP stalls
Detects when buyer-owned mutual action plan steps have been idle past their due date and escalates with a Slack alert to the AE plus an email summary to the account executive's…
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.