← All tools

Alert

Slack alerts when a Salesforce or HubSpot record changes

Tell each record's owner something, over Slack, in the place they already work.

SalesforceHubSpot

A change nobody saw in time. The thing that mattered happened in the CRM and stayed there. The owner was not looking, the report runs on Monday, and by then the renewal conversation has already gone badly.

Alerting is the tool that writes nothing to a record and still changes the outcome.

It is addressed, not broadcast. Each record's own owner is told about their own record, resolved through the mapping between your CRM users and your Slack workspace, so the message lands as a direct message rather than in a channel everybody has muted.

What is worth interrupting somebody for is configuration. The policy is saved under Rules, and it is the one configuration in the product that is not keyed to a CRM object, because an alert acts on nothing. It reports that something happened.

How a pass runs

From scope to record.

  1. Connect. Slack is connected once, and CRM users are matched to Slack users.
  2. Configure. The policy says what kind of change is worth an interruption.
  3. Scope. A run names the records to report on.
  4. Resolve the owner. Each record's owner is looked up and mapped to the person to message.
  5. Send. Each owner receives one message about their own records.

The detail

What it needs and what it does.

Object
Accounts, contacts and leads.
Configured in
Rules, under Alert Policy.
What it writes
A Slack message to the record's owner. No CRM field is changed.
Who releases it
You choose when you create the run: send on dispatch, or hold the run for approval first.
Reversible
Nothing in your CRM is changed, so there is nothing to put back. The run and what it sent are recorded.
CRMs
Salesforce and HubSpot.

Addressing

An alert everybody gets is an alert nobody reads.

The difference between a notification and a channel is who it is for.

The usual failure of CRM alerting is volume without address: a firehose into one channel, which becomes noise within a week and is muted within two. The signal was real and it still did not reach anybody.

Routing to the record's own owner changes the economics. A rep gets a message about their own account, which is the only kind they will keep reading, and the person who can act on it is the person who received it.

For agents

The tools your agent calls.

Reads are free and need no permission to write. Anything that changes a record is a separate grant.

list_crm_users the owners an alert can reach read
create_alert_run a run over a scope you name write
dispatch_run start it write
← All tools Verification →

Where to start

Find out how many you have.

The readiness scan runs detection against your own CRM and reports what it finds, before anything is merged.

Run a readiness scan Request a demo