Signal routing — getting the right change to the right place

Intelligence that stays inside a tool is intelligence nobody acts on. Rules is DatIQ's if-this-then-that layer: it watches for the things you care about and pushes them where your team already works.

Open Rules from the top bar.

Building a rule

A rule is three parts:

1. Trigger — where the signal comes from: a competitor watchlist change, a bulk enrichment

result (for example, an account crossing your ICP threshold), or a workflow run finishing.

1. Conditions — which of those events actually qualify. Materiality is at least high; the ICP score is

above 80; the domain is in this set. Conditions are combined, and an event has to satisfy all of them.

1. Action — what happens: post to Slack, send an email, call a webhook, or create or update

a record in HubSpot.

Test it before you trust it

Every rule has a Test with sample payload button. It runs your conditions against a realistic event and shows you both the verdict and why — which conditions matched and which did not. The preview and the live runtime share the same evaluation engine, so a rule that previews as matching is a rule that will match. A preview that could disagree with production would be worse than no preview.

What happens on every attempt

Each dispatch is recorded whether it succeeded or not, with the outcome and the response. A destination that was unreachable is retried on a backoff schedule rather than dropped silently. You can see the execution history on the rule itself, so "did that fire?" has an answer.

Destinations are re-validated at the moment of dispatch, not only when you saved the rule — a webhook URL that was fine last month and points somewhere it should not today is refused.

Plan note. Signal routing pushes into the same destinations as the Integrations feature, so it is
available on the Select plan and above (see §18).