Expandi → Microsoft Teams

Get real-time Expandi notifications in your Teams channel. Set up in under 2 minutes.

1 Create a Teams Incoming Webhook

In Microsoft Teams, go to the channel where you want notifications.

Click the ••• menu next to the channel name → Connectors (or Manage channel → Connectors).

Find Incoming Webhook and click Configure.

Give it a name (e.g., "Expandi Notifications"), optionally upload an icon, then click Create.

Copy the Webhook URL that appears.

Using the new Workflows app? Create a workflow with the "When a Teams webhook request is received" trigger. The generated URL (ending in .logic.azure.com) works too.

2 Generate your Expandi endpoint

Paste your Teams webhook URL below to generate a unique Expandi endpoint.

3 Add the endpoint to Expandi

In Expandi, go to LinkedIn Account → Settings → Webhooks.

Click Add a webhook, paste the generated URL, and select the event you want (e.g., Contact replied to campaign message).

Save and you're done! Notifications will appear in your Teams channel.

4 Send a test notification

Verify everything works by sending a sample notification to your Teams channel.

Message preview

Here's how a reply notification looks in Teams:

E
Expandi Notifications  · Just now
💬 New Reply
Campaign: ABM | Email vs LinkedIn Research · Sender: Ilija Cosic
Sarah Chen
VP of Sales at TechCorp
TechCorp · 201-500 employees · San Francisco, US
💬 Their reply:
Hey! Interesting question — we've actually been doing a lot more LinkedIn lately since email open rates have been trending down for us.
📤 You sent:
doing a bit of research on the side trying to figure out whether outbound teams are getting better responses from email or LinkedIn these days.
Steps before reply: 3 · Connected: Mar 15 · Replied: Mar 17
🔗 LinkedIn 📥 Expandi Inbox 🔎 Sales Nav

FAQ

Which events are supported?

All 27 Expandi webhook events: replies, connections, messages sent, profile visits, email events, and more. Each event type has its own formatted card.

Is my webhook URL stored anywhere?

No. Your Teams webhook URL is encoded directly into the endpoint path using Base64url. There is no database — the URL is decoded on every request. Fully stateless.

Can I use the new Workflows webhook instead of Connectors?

Yes! Microsoft is transitioning from Office 365 Connectors to the Workflows app. If your webhook URL ends in .logic.azure.com, it will work the same way. Both URL formats are supported.

Can I set up multiple channels?

Yes. Create a separate webhook for each channel, generate a separate endpoint for each, and add each to Expandi for different events (or the same event to multiple channels).

The test says "target URL could not be reached"

Make sure you copied the full generated endpoint URL. It's long because your Teams webhook URL is encoded in the path. Also ensure your Teams webhook is still active and hasn't been deleted.

I'm not receiving notifications

1. Send a test using the button above to verify the endpoint works.
2. In Expandi, check that the webhook is enabled and the event type matches your campaign actions.
3. Webhooks only fire for new events — they don't backfill historical data.