⚡ Workflows is in beta and available to selected customers, with general availability planned in November 2026. Some parts are still being added — see Current limitations below.
Workflows let you automate actions in trumpet so they happen on their own when something happens in another tool — for example, creating a pod the moment a call ends or a deal reaches a certain stage. No one has to open trumpet and fill anything in by hand.
What you can do in this beta
A workflow is made of steps an admin adds. In this beta you can:
Create a pod from a template — clone one of your pod templates and fill in details like company name, domain, and deal value. A workflow can also find the deal’s existing pod instead of making a new one.
Add saved pages and widgets to the pod.
Hide or unhide pages — for example, reveal your pricing page once a deal reaches Proposal.
Build or update a Mutual Action Plan (MAP) from a call, using AI.
Branch with if/else — only run a step when certain conditions are met, for example only creating a pod when the deal value is above a set amount. Conditions can be combined with And or Or.
Email the rep when something happens in the workflow.
You build workflows on a visual canvas, and Copilot can help you draft them.
Coming at general availability: a Copilot step that reads a call and the pod, then updates the pod for you.
How it works
A workflow is set up once by an admin, then runs automatically each time it's triggered.
Setup (admin, once). A brand admin first turns Workflows on in Settings. The workflow itself is then built in the Workflows area: create one from the "New pod automation" template, choose the pod template to clone, set who it runs for (see Who the pod is created for below), and map the details the trigger will send to the fields the pod template needs. Switching on the Enable toggle and saving makes it live.
Trigger (every time). A workflow can start from:
HubSpot — when a deal is created, or when a deal changes stage
Gong — when a call happens
Salesforce — through a Salesforce Flow your admin sets up
Any tool that can call trumpet’s API — a script, or a no-code tool like Zapier or n8n
trumpet confirms straight away that the run has started.
Note on Salesforce: the Salesforce trigger runs through trumpet’s API via a Salesforce Flow — there’s no Salesforce option in the trigger menu, and it needs a Salesforce admin to set up. A step-by-step setup guide is on the way; in the meantime, your Customer Success Manager can help you get it connected.
Still coming: using a trumpet signal from the Nerve Centre as a trigger.
What trumpet does. If your tool already sends structured details (company name, domain, deal value), trumpet maps them straight into the new pod — no AI involved. If it only sends free text, the optional AI step reads it, pulls out those details, then creates the pod.
You don't need a Gong account, a Zapier account, a specific CRM, or to be logged in to trumpet for a workflow to run. You just need a trumpet API key and a way to call the API.
This is not Copilot. Copilot is the AI assistant you chat with inside trumpet. Workflows run in the background and are started by another tool, not by clicking inside the app.
Who the pod is created for (enrollment)
Enrollment decides who a workflow runs for. It's set inside trumpet before the workflow is switched on — not in the API call. When a workflow is triggered, trumpet starts one run for each enrolled person.
Setting | Who is enrolled |
For me | Just the person setting it up |
For specific teams | Everyone on the chosen teams |
For specific departments | Everyone in the chosen departments |
For entire brand | All active users in the company |
⚠️ Important: because a trigger runs for every enrolled person, one event can create several pods at once. If 12 reps are enrolled and one call finishes, a single trigger creates 12 pods. To avoid this, keep enrollment narrow — set it to For me or a single user (or a small, specific team) so each trigger creates the pods you actually want.
You can also set who owns each new pod — a fixed teammate, or the enrolled person the run is for. Admins can additionally choose whether members can opt in or out of a workflow, or lock it so only admins can switch it on or off.
Checking your workflows and runs
Workflows page — lists your workflows and their current status.
Workflow history — shows each run with its status (Queued, Running, Completed, Failed, or Cancelled) and its start and completion times, so you can see whether a run finished successfully.
What you need to get started
If you’re using a native trigger (HubSpot or Gong), you just connect that integration — no API key needed. For API or Salesforce triggers you’ll need:
A trumpet API key for your brand.
The workflow's endpoint URL, which you get once the workflow is created and switched on.
A way to call the API — a script, or a no-code tool like Zapier or n8n if you don't have a developer.
Someone technical on your side sets this up. It isn't a one-click switch: a person needs to build the workflow in trumpet and connect your trigger tool to trumpet's API.
Using Workflows alongside existing auto-creation
If you already create pods automatically through HubSpot or Salesforce, we recommend keeping that switched on until you've tested your workflow and confirmed it works, since Workflows is still in beta. You can also set up more than one workflow at a time, each with its own trigger.
Current limitations
For API and Salesforce triggers, you set up the connection yourself — trumpet doesn’t build or host it for you.
trumpet doesn’t notify your own tools when a run finishes, but you can check the status on the Workflow history tab.
There’s no approval step yet before an action runs.
FAQ
What is an API call?
An API is how two pieces of software talk to each other directly, without anyone clicking through a screen. An API call is one request from one system to another. Here, your tool sends a request to trumpet with the event details, and trumpet creates the pod. It all happens behind the scenes.
Do I need a developer?
Not necessarily. If you're comfortable writing a script, that works. If not, a no-code tool like Zapier or n8n can send the request for you. Either way, someone on your side builds the connection.
What's the difference between Zapier and n8n?
Both send data from one tool to another when something happens, without writing code. Zapier is more plug-and-play with a large app library; n8n is open source and more flexible for teams who want to self-host or build more complex logic. Either can point at trumpet's API.
Does it use AI to read my calls?
Only if it needs to. If your tool sends structured fields like company name and deal value, no AI runs. If it only sends free text like a transcript, an optional AI step pulls out the details first.
Is this the same as Copilot?
No. Copilot is the AI assistant you chat with inside trumpet. Workflows are background automations started from another tool.
What does the conditions (if/else) step do?
It lets a workflow behave differently depending on the details it receives — for example only creating a pod when a deal value is above a certain amount. Each path can combine several conditions using And or Or, and whatever step sits on a path only runs when that path's conditions are met.
Can a workflow hide or unhide a page?
Yes, it can work in this beta. Hiding and unhiding pages is handled by other tools in trumpet (such as pod tools), not as a workflow step yet.
Need a hand? Reach out via the chat bubble or email our support team. 🎺