Preparation nobody has time for, delivered before the call
Every rep knows they should research before a call. Almost no one does it between back-to-back meetings, so the first ten minutes are spent recovering context the CRM already held.
The information is not missing. It is scattered across a calendar entry, a CRM record, and an email thread. Assembling it takes longer than the preparation is worth for a person with four calls that afternoon.
Assembly is exactly the kind of work that should not involve a person. What should involve a person is the judgment afterward: reading the page, noticing the open item from six weeks ago, and deciding what to open with.
Length is the constraint that makes this usable. A brief that runs past one screen is not read on a phone between meetings. A brief that is not read is the same as no brief.
How the ActionFlow runs on the canvas
A Start Scheduled node fires ahead of the calendar, and an HTTP Request node reads the day's external meetings from your calendar.
An If node immediately filters out internal calls. Briefing every meeting turns a useful notification into noise reps mute within a week.
For the meetings that survive the filter, a HubSpot or Salesforce node pulls the account record and recent activity, and an HTTP Request node retrieves any data stored outside the CRM.
A Generate Text node writes the brief to a fixed shape: attendees, what the company does, what has happened between you, open items, and two suggested questions. Constraining the shape keeps the length predictable across accounts of different sizes.
A Slack node delivers it to the rep. Delivery into the channel they already have open beats email, which they read after the call.
A String node truncates anything over the length you set, so a large account with years of history produces the same one-screen brief as a new account rather than an essay.
Nodes this ActionFlow uses
- Start Scheduled: runs ahead of the day's calendar rather than on each event.
- Google (Integration): reads the calendar entries and attendees.
- If (Control): removes internal meetings so the notification stays worth reading.
- Salesforce (Integration): pulls the account record and recent activity. HubSpot fits the same slot.
- HTTP Request (Util): retrieves context held outside the CRM.
- Generate Text (AI Core): writes the brief to a fixed shape so length stays predictable.
- String (Util): enforces the length limit that makes the brief readable on a phone.
- Slack (Communication): delivers it where the rep already is.
Frequently asked questions
Start building AI workflows
Create a free account, open a template or a blank canvas, and run your first ActionFlow.
Newsletter
Get product updates
New nodes, agents, and product notes. We send mail only when we have something worth opening.