Choose the Teams path

For new Microsoft Teams setups, prefer a Teams Workflow that starts from a webhook request when available in your tenant. Legacy incoming webhook connectors may still work in some tenants, but Microsoft is moving Teams connector scenarios toward Workflows.

Teams setup

  • Create a Teams workflow with a webhook trigger, or create an incoming webhook connector if your tenant still supports it.
  • Select the team and channel where sales or operations should receive lead alerts.
  • Copy the generated webhook URL.
  • Paste the URL into `/settings` in InstaChime and save.
  • Send an alert test from `/integrations`.

Verify

  • Confirm the Teams message or card renders in the target channel.
  • Confirm the message includes name, phone/email, source, and message text.
  • Confirm the webhook URL is stored only in InstaChime settings and not in public docs or client-side code.
  • Confirm failed Teams deliveries appear in `/integrations`.

Legacy incoming webhook setup

  • Use this path only if your tenant still allows incoming webhook connectors.
  • Open the Teams channel.
  • Open channel management or connectors.
  • Add Incoming Webhook.
  • Name the webhook `InstaChime Leads`.
  • Copy the generated URL.
  • Paste it into InstaChime settings and send an alert test.

Teams troubleshooting

  • If new connectors are blocked, use the Workflows webhook trigger path instead.
  • If the card does not render, test a minimal Adaptive Card in Postman against the Teams webhook URL.
  • If the workflow owner leaves the company, transfer or recreate the workflow under a durable owner.
  • If messages post to the wrong place, recreate the workflow for the intended team/channel or chat.
  • If Teams returns an auth or permission error, confirm the workflow owner still has access to the destination.

Official references

These vendor-owned pages explain the controls and requirements referenced in this guide.