Skip to article

Integrations

Slack

A Slack workspace and channel for drafts, approvals, and updates

Ownership and availability

You own the Slack workspace and channel. Obelo manages the Slack app and stores the workspace authorization server-side.

Start in Settings → Integrations and check the provider’s current status. This guide describes the configured setup path, not a guarantee of production enablement. Provider approval, plan access and resource permissions still apply.

Before you connect

  • Permission to install apps in the Slack workspace, or workspace-admin approval
  • A public or private channel Obelo may access
  • An Obelo workspace owner or admin completes OAuth and channel selection

Connect an existing account

  1. Open the provider in Settings → Integrations for the intended website.
  2. Authorize the Obelo Slack app for the target workspace
  3. Approve the requested channel-list and message permissions
  4. Return to Obelo and select the channel for drafts and approvals

If you need a new resource

  1. Create a Slack workspace or choose an existing one
  2. Create a dedicated Obelo marketing or approvals channel
  3. Ask a Slack admin to allow the Obelo app if installations are restricted

Permissions to check

  • channels:read and groups:read discover eligible channels
  • chat:write sends drafts and approval updates only to the selected channel

Verify and troubleshoot

After the channel and app access are ready, return and reload the channel list.

Slack returned no selectable channels. Create a channel, invite the Obelo app where required, or ask a Slack admin to grant access.

Confirm the selected account or resource and inspect the verification or sync result. A saved connection is not proof that an import or publication has completed. Test the intended workflow with an appropriately reviewed item.

Disconnect or change access

Use the provider’s management controls in Obelo to disconnect when supported. Revoke the grant or rotate a dedicated credential at the provider if access must end immediately. Review already-imported data separately; disconnection does not remove content already published elsewhere.

Something unclear or out of date?

Suggest a correction