Slack bridge

Few teams leave Slack in a day, and a move that strands half the team in the old tool usually doesn't happen at all. The Slack bridge keeps a Slack channel and a OneCamp channel in one conversation while you move:

• What someone writes in Slack appears in OneCamp, led by their name.
• What someone writes in OneCamp appears in Slack, under their name.
• Thread replies, edits and deletions follow, both ways.

People in Slack don't need a OneCamp account, and they take no seat.

It is in both editions. If Admin, Integrations has no Slack bridge card, update to the latest release first.

Connect Slack

You need to be an admin in OneCamp and able to install apps in your Slack workspace.

1. In OneCamp, open Admin, Integrations, Slack bridge and press Create the app in Slack. Slack opens with the app already described: its name, the permissions it needs, and where to send messages. Choose your workspace and create it.
2. In Slack, press Install to Workspace and allow it.
3. Copy two values back into OneCamp:
   • Bot User OAuth Token (starts with xoxb-), from OAuth & Permissions.
   • Signing Secret, from Basic Information.
4. Press Connect Slack. OneCamp checks the token with Slack before saving it, and stores both values encrypted.

Slack must be able to reach your server: it delivers messages to https://<your API host>/slack/events. On a normal install that is already public. The card shows the exact address.

Link channels

Pick a Slack channel and a OneCamp channel and press Link. Each channel can belong to one link.

• Public Slack channel: the app joins it by itself.
• Private Slack channel: type /invite @OneCamp in that channel first.

Linking a private OneCamp channel to a Slack channel shows its messages to everyone in that Slack channel, so link it only to one with the same people.

What you will see

In OneCamp, Slack messages come from an account called Slack, and each starts with the sender's name, for example [Priya]. In Slack, OneCamp messages show the author's name with the app's icon.

• Formatting carries over: bold, italics, strikethrough, code, links and lists.
• Files shared in Slack arrive as links to the file in Slack.
• A reply in a Slack thread becomes a reply on that message in OneCamp, and the other way round, when the message it replies to came across the bridge.
• Replies from agents and workflows stay in OneCamp.
• Messages from before a link was made are not copied. To bring history over, use Admin, Import, Slack with an export.

When something goes wrong

If Slack refuses a message, the card says why and what to do: for example, reinstall the app because its token was revoked, or invite it into a channel it was removed from. Delivery resumes by itself once that is fixed.

Disconnect stops every link at once. Messages already bridged stay in both apps.