What lands in Notion
One database item per signal. The portal probes your database when you connect it and lets you match our fields (name, signal type, strength, title, company, ICP scores, summary, why it matters, the portal link) to the columns you already have. Fields you leave unmapped are skipped.
Connect it
- In Notion, create an internal integration and copy its token. Share the target database with that integration.
- In Destinations, choose Add destination, then Notion. Paste the token and the database ID.
- Map our fields to your properties. Unmapped fields stay out.
- Use Test connection to create a sample item.
One signal, arriving
Signals database
Name: Marcus Feld · Brightmile
Strength: 8 · Signal type: competitor engagement · ICP: RevOps leader
Why it matters: renewal pressure at a 200-person company inside your ICP.
Details
| Connection | Notion internal integration token plus the database ID. |
|---|---|
| Mapping | Per-destination property map, set from a probe of your database. |
| Limits | Rich text fields are cut at Notion's 2,000-character limit. |
| Plans | Included in every plan. |
Good to know
- The Notion API rejects unknown property names, which is why the mapping step exists.
- Reconnect the destination after renaming a property in Notion so the map stays current.
Related
- Google Sheets → Each qualified signal becomes one row, with fixed columns your dashboards and other tools can read.
- Slack → Every qualified signal lands in the channel you pick as a card with the score, why it matters, and a link to the full signal.
- Clay → Point a Clay webhook source at SignalRaven and every qualified signal arrives as a row, ready for enrichment and sequencing.