Bring the update
to the conversation.

Connect Slack.

1. As a Business workspace owner or admin, open Notifications → Slack → Connect Slack.
2. In Slack, select the correct Slack workspace and channel, then authorize PageFluxer. Your Slack organization may require an admin to approve the app.
3. Back in PageFluxer, check the saved destination label and choose Send test. Confirm the card appears in Slack.
4. Enable Slack delivery on the monitors you want in that channel.

The connection requests Slack’s incoming-webhook permission for one selected channel. PageFluxer does not read your Slack messages. The destination belongs to the PageFluxer workspace, even if the person who connected it leaves. Slack can independently revoke access or disable an app; reconnect if delivery stops.

Use Change Slack channel to replace the destination. Waiting deliveries for the old destination are cancelled. This release supports commercial Slack workspaces through hooks.slack.com, with one Slack destination per PageFluxer workspace.

Connect a Teams Workflow.

This integration uses Microsoft’s Workflows app, rather than a legacy Office 365 connector. It sends an Adaptive Card to the destination your workflow selects. Your Microsoft organization must allow Workflows, and its own licensing and policies apply.

1. Open Workflows in Teams. Choose the template that sends webhook alerts to a channel, or create a flow with the When a Teams webhook request is received trigger.
2. Set the trigger’s allowed callers to Anyone. PageFluxer uses the generated signed URL as the secret; it does not obtain a Microsoft user access token. If your organization forbids this option, this connection method is unavailable.
3. Choose the team and channel and sign in to the Microsoft connection requested by the workflow.
4. Confirm the workflow posts each Adaptive Card from the incoming attachments array. For a custom flow, add Apply to each over triggerBody()?['attachments'], then Post card in a chat or channel with card content item()?['content']. Use the flow bot and your chosen channel. Do not paste the entire request envelope into the card-content field.
5. Save the flow. Copy the complete signed trigger URL, including its query string. In PageFluxer, open Notifications → Microsoft Teams, give it a recognizable label and paste the URL.
6. Choose Send test. Check the Teams channel and the Workflow run history. HTTP acceptance alone does not prove that the later posting step succeeded.
7. Add a trusted co-owner to the Microsoft workflow. Microsoft workflows belong to individual accounts; a PageFluxer admin role does not grant ownership of the Microsoft flow.

PageFluxer accepts signed Workflow endpoints on Microsoft’s logic.azure.com and api.powerplatform.com hosts. Legacy webhook.office.com connectors, arbitrary proxy URLs, and Microsoft sovereign-cloud endpoints are not supported in this release. If Microsoft rotates the trigger URL, replace it here and test again.

{
  "type": "message",
  "attachments": [
    {
      "contentType": "application/vnd.microsoft.card.adaptive",
      "contentUrl": null,
      "content": {
        "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
        "type": "AdaptiveCard",
        "version": "1.2",
        "body": [
          {
            "type": "TextBlock",
            "text": "PageFluxer found a change.",
            "wrap": true
          }
        ],
        "actions": [
          {
            "type": "Action.OpenUrl",
            "title": "Review change",
            "url": "https://pagefluxer.com/dashboard"
          }
        ]
      }
    }
  ]
}

Microsoft’s Workflow webhook instructions ↗

Connect once. Choose each monitor.

On a monitor’s details page, use Notifications for this monitor to select Slack or Teams. Members can choose any workspace destination that an admin has connected; members cannot read its secret URL or replace the destination. Channel delivery starts with future changes that match the monitor’s alert rules.

Email, generic webhooks, Slack, and Teams are independent. You can enable channels with email off. Email alerts go to the workspace owner’s sign-in address and follow the workspace email schedule; each member does not automatically receive a separate email. Channel cards ignore email quiet hours and digests.

Useful delivery history, with bounded retries.

Recent deliveries appear in Notifications. “Sent” means the email provider or channel endpoint accepted the request. It does not mean someone read it, and a Teams Workflow can fail after accepting the request.

Business includes 30,000 outbound attempts per calendar month, shared by generic webhooks, Slack, and Teams. Failures, retries, and connection tests use attempts. Matching a monitor’s rule does not use an extra check. Native channel sends are paced to one attempt per second per destination.

Temporary connection failures, HTTP 429 and server errors retry with backoff, up to ten attempts within 23 hours of the first attempt. A bounded Retry-After delay is honored. Permanent client errors stop automatic retries. Owners and admins can retry an eligible failed delivery inside that window while the same connection and allowance remain available. Delivery is at least once: retries after an ambiguous response can cause duplicate channel posts.

Disconnecting, replacing a destination, disabling that monitor’s channel, losing Business access, deleting the monitor, or expiry of the underlying history cancels waiting delivery. A request already in flight may finish. Reconnecting sends future matching changes; it does not replay cancelled history. Completed delivery metadata is kept for seven days.

Share only with the right audience.

Cards include the monitor name, a bounded explanation or captured excerpt, detection time, and a PageFluxer link. A saved AI summary can be included when available. Your Slack/Teams channel may include people who do not belong to the PageFluxer workspace: those people can read the card, but must have PageFluxer workspace access to open its private history.

Private screenshot URLs, signing keys and API tokens are not posted. Destination URLs are encrypted in PageFluxer’s database. Treat Microsoft Workflow URLs as passwords and keep the notification encryption key backed up on your server. Disconnecting a destination does not delete messages already stored by Slack or Microsoft.