Reach your users in Microsoft Teams, from the same Notifly workflow.

These are the fields the dashboard asks for when you connect MSTeams, quoted from the create form. All four are optional, and the form says why: “These credentials are only required for Bot App authentication and are not needed for incoming webhook functionality.”

• For a webhook only. Leave all four empty and save each subscriber's webhook URL instead.
• For your bot. Fill in the Microsoft App ID, Client Secret and Directory (tenant) ID, and add https://api.notifly.io/v1/integrations/chat/oauth/callback as a redirect URI on the Azure app registration.
• Redirect URL in Notifly. Optional: where users land after connecting. Left empty, Notifly shows its own confirmation page.

1. Sign in at app.notifly.io, open Integration Store in the sidebar and choose Connect Provider.
2. In the Connect Integration sheet, open the Chat tab (or search across channels), find MSTeams and choose Connect.
3. Pick the environment the integration belongs to. Development and Production keep separate integrations, so you can point each at a different MSTeams account or key.
4. Fill in Delivery Provider Credentials with the fields in the table above, then choose Create Integration.

Save a webhook URL or send the user through a connect link once; after that a trigger only names the subscriber, and Notifly works out where in Teams the message goes.

// npm install @notiflyio/api@0.1.26
import { Notifly } from "@notiflyio/api";

const notifly = new Notifly({ security: { secretKey: process.env.NOTIFLY_SECRET_KEY } });

// Option A: an incoming webhook URL your user created in Teams. No bot needed.
await notifly.subscribers.credentials.update(
  { providerId: "msteams", credentials: { webhookUrl: teamsWebhookUrl } },
  "user_123",
);

// Option B: your own bot. A connect link (valid for 5 minutes) asks the user's tenant admin
// for consent; autoLinkUser then signs the user in and installs your bot for them.
const { result } = await notifly.integrations.generateConnectOAuthUrl({
  integrationIdentifier: "msteams-bot", // the Identifier of your MSTeams integration
  subscriberId: "user_123",
  autoLinkUser: true,
});
// Redirect the user to result.url.

// Either way, workflows with a chat step now reach them in Teams.
await notifly.trigger({
  workflowId: "incident-opened",
  to: "user_123",
  payload: { service: "billing-api", severity: "high" },
});

Prefer plain HTTP? The same trigger is POST https://api.notifly.io/v1/events/trigger with an Authorization: ApiKey header and a body of { "name", "to", "payload" }.

• A webhook post. The chat step's content, sent as is when it is JSON and as { "text" } when it is not, after a safety check on the address.
• Workflows webhooks. Microsoft 365 Connectors are nearing deprecation, and Microsoft points to webhooks created with the Teams Workflows app instead (Microsoft Learn). Their trigger takes Adaptive Cards or a Message Card (Microsoft Learn), so for a Workflows webhook URL write the chat step's content as Adaptive Card JSON: a message with application/vnd.microsoft.card.adaptive attachments, which Notifly posts as is.
• Or a bot message. For a linked user or a channel, a Bot Framework message sent with an app-only token Notifly requests with your App ID and client secret.
• Teams' answer. A refusal fails the step with a named MSTEAMS error or Teams' own, recorded in the activity feed.