> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Slack on Vortex IQ

> Monitor Slack performance signals, run automated checks, and prepare approved work through Vortex IQ.

Monitor Slack performance signals, run automated checks, and prepare approved work through Vortex IQ.

[Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [How connecting works](/integrations/connector-catalogue) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=slack)

<CardGroup cols={5}>
  <Card title="5">
    performance signals
  </Card>

  <Card title="None yet">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="174">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup cols={2}>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    No changes are made without the configured approval policy. Read-only operations do not modify the connected system; schedules, access scopes, API usage and data handling remain governed by Vortex IQ controls.
  </Tab>

  <Tab title="Monitor (5)">
    ### Monitor performance

    5 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (4 signals)">
        | Signal                       | Alert behaviour | What it tracks                                                                                                                                                                      |
        | ---------------------------- | --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Delivery Channel Type**    | Watch only      | Constant 'Incoming Webhook' - the delivery mechanism for this connector. States plainly how messages reach this channel.                                                            |
        | **Messages Sent (30d)**      | Watch only      | Count of messages delivered in the last 30d. Degrades to no\_data (reason not\_tracked): an incoming webhook exposes no history/read method, so sent vol                            |
        | **Slack Channel Configured** | Watch only      | Renders 'Connected' when webhook\_url is present and matches ^[https://hooks.slack.com/](https://hooks.slack.com/), else 'Not connected'. Pure credential-shape check, no API call. |
        | **Webhook Host**             | Watch only      | Host parsed from webhook\_url (expected hooks.slack.com). Confirms the pasted URL targets Slack, not some other host.                                                               |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal                   | Alert behaviour | What it tracks                                                                                                                                            |
        | ------------------------ | --------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Last Delivery Status** | Watch only      | Result of the most recent send. Degrades to no\_data (reason delivery\_log\_unavailable): no send log is persisted yet, and an incoming webhook has no re |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (0)">
    ### Audit risks and opportunities

    No automated checks are defined for Slack yet. The performance signals cover the monitoring layer, and checks arrive with the connector's audit module.

    #### Build your own automated fixes

    Turn any finding into an automated fix with a Vortex IQ workflow: **over 13,000 read and write operations across more than 200 connectors** are available as building blocks, with approval, verification and rollback on every change.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **80 read** and **94 write** operations across admin.apps.approves, admin.apps.approved.lists, admin.apps.requests.lists, admin.apps.restricts, admin.apps.restricted.lists, admin.conversations.archives on Slack. Combine them with anything from the **over 13,000 operations across more than 200 connectors** to automate the work in your own words.

    Changes follow your configured approval policy: the target, proposed change, affected records, risk, reversibility and verification plan are shown before execution.

    [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=slack)

    #### Ready to build your first Slack workflow

    Pick a trigger, add the operations above as steps, and every step that changes data pauses for your approval. Monitoring and audits are live now and can start any workflow you build.

    <Accordion title="Browse the operations you can build with">
      | Resource                              | Read operations | Write operations |
      | ------------------------------------- | --------------- | ---------------- |
      | admin.apps.approves                   | 0               | 1                |
      | admin.apps.approved.lists             | 1               | 0                |
      | admin.apps.requests.lists             | 1               | 0                |
      | admin.apps.restricts                  | 0               | 1                |
      | admin.apps.restricted.lists           | 1               | 0                |
      | admin.conversations.archives          | 0               | 1                |
      | admin.conversations.converttoprivates | 0               | 1                |
      | admin.conversations.creates           | 0               | 1                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>