Connected delivery

One signal. Every destination you already use.

Some paths are native delivery, some work alongside tools you own, some are API or webhook handoff. We keep those categories separate — on purpose.

SIGNAL
Slack
Teams
HubSpot
Email
API / Webhook
How we say it

We tell you exactly how each tool connects.

Native = we build & run itAlongside = your license, our workflowHandoff = your system pulls / we push
01

Native delivery

Native

Signals land in the systems your team already uses for follow-up.

Slack

Live

Real-time alerts with full context. Feedback buttons built in — mark signals helpful or irrelevant, and the system learns.

Microsoft Teams

Live

Adaptive Cards delivered to any channel — same intelligence, same speed, native to your Teams workflow.

Email Digests

Live

Daily and weekly summaries — every signal from the last 24 hours or 7 days, prioritized and ready to act on.

02

Native CRM sync

Native

HubSpot is the native CRM workflow today. Everything else is honest API handoff.

HubSpot

Native

One-click OAuth. Target accounts import automatically. Account scores push to custom properties every 6 hours. Owner data, lifecycle stages, and engagement flow into scoring — CRM and intelligence stay in sync.

OAuth · Auto target import · Scores push / 6h

Other CRMs

API + Webhooks

Pipedrive, Zoho, Close, Copper and similar stacks receive signal data via API or outbound webhooks. That is a handoff workflow — not the same as native in-app sync.

03

Works alongside

Alongside

These aren’t ours — we work with the license you already pay for, and say so.

Apollo

Customer license

Ops Center and Enterprise use your Apollo license for target-account discovery and buyer-persona contact sync. Apollo stays your data source; Amplify handles matching, monitoring, and delivery around it.

ZoomInfo

Customer license

Ops Center and Enterprise can use your ZoomInfo license for target-account and buyer-persona contact data. ZoomInfo stays your data source; Amplify handles matching, monitoring, and delivery around it.

LinkedIn Ads

Paid add-on

Signal-driven LinkedIn audience workflows are a paid add-on for paid-media orchestration — an alongside workflow, not a core delivery surface.

04

API + webhook handoff

Handoff

The honest way to connect internal tools, warehouses, Clay, Zapier, Make, n8n.

REST API

Pull

Query signals by domain, account, or time range. Pull intelligence into internal tools, enrichment tables, and data workflows on demand.

Outbound Webhooks

Push · HMAC

Real-time POST to any URL when a signal is detected. HMAC-signed payloads, automatic retries, and full event context.

Delivered

One signal, delivered four ways.

A P1 fires once — and lands everywhere your team works, instantly.

Slack priority alert instant
HubSpot dated task owned
Email in the digest daily
Webhook to your stack HMAC
AmberAPP12:48 PM
LAYOFF ALERT: Johnson & Johnson

Johnson & Johnson trimmed its New Jersey headcount by 56 employees, according to a BioSpace layoff tracker update.

100· Opp · Last activity 23d ago ·@Jess Schultz
No overclaiming

The honest connection matrix.

Every path, stated plainly — who runs it, how it authenticates, which way data moves.

Connection
Who runs it
Auth
Direction
Native delivery
We build & run it
OAuth / app
Push to channel
Native CRM (HubSpot)
We build & run it
OAuth
Two-way sync
Works alongside
Your license
Your tool’s auth
Coordinated
API + webhook
You integrate
API key / HMAC
Pull or push
Questions

Before you connect it.

What does “Native” actually mean?
We build and run the integration end to end — Slack, Teams, Email, and HubSpot. You don’t wire anything up; signals arrive in-app with full context.
Do we need our own Apollo, ZoomInfo, or LinkedIn license?
Yes. Apollo and ZoomInfo (on Ops Center and Enterprise) and the LinkedIn Ads add-on use licenses you already pay for — we coordinate the workflow around the seat you own, we don’t resell the underlying tool.
How do webhooks authenticate?
Outbound webhooks are HMAC-signed with automatic retries and full event context, so your endpoint can verify every payload before acting on it.
Can the API pull on our schedule?
Yes. The REST API lets you query signals by domain, account, or time range — pull intelligence into internal tools, enrichment tables, or your warehouse on demand.
Tell us your stack

We’ll show you exactly how it connects.

If your team uses a tool that can receive data by API or webhook, we can usually hand signals off to it — and we’ll describe the real model, not imply a native integration that doesn’t exist.