SALES
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.
How it runs
The automated pipeline, trigger to output.
- TriggerHourly schedule checks API volume
- ActionQuery product DB for surge vs rolling baselinePostgres
- LogicRequire sustained surge to qualify as PQL
- ActionCreate/advance expansion opp in SalesforceSalesforce
- LogicRoute by segment to owning rep
- OutputAssign HubSpot follow-up task with contextHubSpot
What it does
Treats a sustained API-traffic surge as a product-qualified expansion signal. It confirms the surge is real (not a one-off spike) against a rolling baseline, marks the account as a PQL, advances or creates the expansion opportunity in Salesforce, and routes a follow-up task to the correct rep by segment.
When to use it
Use this for usage-based or API-metered products where rising consumption is the clearest buying signal. It closes the gap between "the account is clearly scaling" and "someone actually owns the expansion conversation."
How it works
- 1A schedule queries the product database hourly for accounts whose API volume exceeds their 30-day rolling baseline by the configured factor.
- 2A logic step requires the surge to persist across multiple intervals before qualifying, filtering out transient spikes.
- 3Qualified accounts are written back to Salesforce as a product-qualified expansion opportunity with the supporting usage metrics.
- 4A branch routes by account segment to pick the owning rep.
- 5A HubSpot task is created and assigned to that rep with the surge context and a suggested outreach angle.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect SalesforceAccounts, opportunities, cases.
- 3Connect HubSpotCRM, deals, marketing, support.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Sales workflows
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…
MEDDIC Gap Sync to HubSpot Deal Properties
Transcribes a finished Zoom discovery call, extracts MEDDIC details, and writes structured values into custom HubSpot deal properties while logging the call as a timeline note.
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.