The problem this solves
Signals are only useful if someone acts on them, and the person who should act is the account owner, who lives in the CRM rather than a Slack channel. A signal posted to a channel is seen by whoever is looking; a task assigned to the owner with a due date is seen by the person responsible and tracked until it is done. The CRM's own task queue is the right place for a signal to land.
The task also needs to be complete enough to act on without research. A task that says 'Acme raised money' sends the owner to a search engine; a task that carries the round details, the source link and a suggested opener lets the owner write the email from the task itself. Due within two days, it keeps the follow-up inside the window when the signal is fresh.
Because the mission watches a list rather than the whole database, it stays focused on the accounts the team has chosen, and because it creates a task only when something moves, it never becomes noise in the owner's queue.
How the mission runs
- Watch list <name> for the three signals. The Signals Agent baselines each company on list <name> and, on a daily cadence, checks funding data for new rounds, hiring data for new <role> postings and technographics for <technology> newly detected. Only changes against the baseline count.
- Look up the account owner. For each company with a new signal, the agent reads HubSpot for the company record and its owner. Companies on the list that are missing from HubSpot are created as a reviewed batch and assigned to a default owner you name.
- Write the task with evidence and an opener. A task is composed with the signal type, the details - round, amount and investors; posting title and date; technology and where it was seen - the source link, and a suggested opening line written from the signal in your voice.
- Create the task due within two days. The task is created in HubSpot on the company record, assigned to the owner, due within two days, and the baseline is updated so the same signal never produces a second task. A daily summary of tasks created is posted to you.
The prompt
This is the exact objective the agent receives. Swap the obvious placeholders for your own domain, segment or channel and run it as-is from the console, Slack, or the API.
What comes back
HubSpot tasks assigned to account owners whenever a company on list <name> raises funding, posts a <role> role or adopts <technology>, each task carrying the signal details, the source link and a suggested opener, due within two days. A daily summary lists the tasks created by signal type, and the list keeps a change history per company so the pattern of signals can be reviewed later.
Make it yours
- Add leadership changes and expansion news as further triggers.
- Create the task in Pipedrive or Attio instead of HubSpot, or an Asana task for teams that work outside the CRM.
- Post a copy of each task to the owner's Slack DM so it is seen immediately as well as tracked.
- Draft a full first-touch email into the task instead of a single opening line.
Frequently asked questions
What if the account has no owner in HubSpot?
The task is assigned to the default owner you name in the prompt and flagged so ownership can be corrected; the mission reports unowned accounts each day.
Will the same signal create several tasks?
No. Each signal is recorded against the company and never repeated; a second round or a second posting is a new signal and gets its own task.
Can the due date be different per signal type?
Yes. For example one day for funding and five for a technology adoption; state the rule in the prompt.