Slack
Connect a Slack workspace to Floqer to read and write your channels. Floqer posts workflow results into a channel, lets your team take action on them from Slack, and imports channel activity into a list.
Connect
- Log in to app.floqer.com and go to Connections → Slack, or open app.floqer.com/connections directly. Add to Slack on floqer.com/slack-app lands on the same page.
- Toggle Enable for Org if other members of your workspace should use this connection.
- Select Connect to Slack. Slack lists the OAuth scopes it will grant. If you belong to several workspaces, pick the right one at the top of that screen.
- Select Allow. Slack returns you to Floqer.
- Open the connection under Connections, toggle Set as Default if this should be your default Slack connection, and select Save Changes.
Careful
If your workspace restricts who can install apps, step 4 becomes a request to a Workspace Owner or Admin. Repeat the steps once they approve Floqer.
Slack does not expire the tokens it issues to Floqer, so the connection stays valid until you remove the app from the workspace or delete the connection in Floqer. You do not need an admin role to install, and Floqer never holds an admin token.
Add the Floqer bot to channels
Open the channel in Slack and run /invite @Floqer, or add the app from the channel's Integrations tab.
| What you want to do | Public channel | Private channel |
|---|---|---|
| Post a message | The bot does not need to be a member | Add the bot first |
| Import the channel | Add the bot first | Add the bot first |
Floqer cannot post to or import direct messages and group messages. Removing the bot from a channel stops any import from it, and rows already imported stay in the list.
What Floqer does with the connection
| Capability | Slack API calls |
|---|---|
| Send a Message action | chat.postMessage, and chat.update when someone clicks a button on a message Floqer posted |
| Channel pickers | conversations.list |
| Slack list source | conversations.history, conversations.replies, conversations.info, conversations.members, pins.list, users.info, team.info, and file downloads from files.slack.com |
Slack actions cost 0 credits. Slack allows an app outside its Marketplace one history call per minute with 15 messages each, so the first import of a channel with a few thousand messages takes hours; later syncs are small and fit the cadence.
Security and access
Note
Security at a glance: Floqer connects over OAuth 2.0, so you never share a Slack password. It acts only as the bot it installs, never deletes anything in Slack, and can be removed from your workspace at any time. Channel membership is the enforceable boundary: Floqer cannot read a channel the bot is not in, whatever a source is configured to do. The one exception is chat:write.public, which lets the bot post to any public channel and grants no read access.
OAuth scopes
Slack does not let you decline individual scopes, so you grant all of these at install.
| Scope | What Floqer uses it for |
|---|---|
channels:read, groups:read | Listing channels in the pickers, reading channel details and members, and detecting which channels the bot is in. channels covers public channels and groups covers private ones. |
channels:history, groups:history | Reading messages and replies in channels the bot is a member of, for the Slack source. |
chat:write | Posting as the bot, and updating a message Floqer posted. |
chat:write.public | Posting to a public channel without adding the bot first. |
users:read, users:read.email | Names, titles, and emails of message authors on imported rows. |
team:read | Your workspace domain, for permalinks. |
files:read | Downloading files attached to imported messages. |
pins:read | Pinned messages on imported channels. |
reactions:read | Reactions on imported messages. |
links:read | Links shared in imported messages, with their previews. |
im:write, mpim:write | Sending a message to a person or a small group directly, outside a channel. |
Slack also issues a user token for the person who installs. Floqer stores it with the connection and makes every call with the bot token instead. Floqer reads only the channels you select on a source and posts only to the channel you select on an action.
Note
Floqer never deletes a Slack message, file, or channel. Its only writes are posting a message and updating a message it posted.
Revoking access
- In Slack: open Manage apps for your workspace at
<workspace>.slack.com/apps/manage, select Floqer, and remove the app. Slack invalidates the tokens immediately. - In Floqer: delete the connection under Connections → Slack.
- For one channel: remove the bot from the channel. Floqer stops reading it and the app stays installed.
FAQs
Why is a channel missing from the picker?
A private channel appears only after you add the bot to it.
Why did a channel stop importing?
The bot was removed from it, or the channel was archived or deleted. Add the bot back and the next sync resumes.
What data does Floqer store?
| Category | Typical items | Direction |
|---|---|---|
| Messages and events | Text, timestamps, thread and channel IDs, permalinks, reactions, reply counts, edit history, pins, membership changes | Read |
| People | Slack user ID, name, title, email, and external flag of authors of imported messages | Read |
| Channels | ID, name, topic, purpose, privacy and shared flags, member count | Read |
| Files | Name, type, size, ID, Slack URL, and a copy of each file on an imported message | Read |
| Messages Floqer posts | The text and form data sent, and the channel, timestamp, and status Slack returns | Write |
| Integration credentials | Bot token and user token, workspace ID and name, bot user ID, and the installing user's Slack ID | Held by Floqer |
| Operational data | Sync cursors, job status, timestamps, API responses and errors | Held by Floqer |
Floqer skips deleted messages, Slack's system notices for joins, leaves, topic, purpose, name, pin, and unpin changes, and messages with the bot_message subtype. Rows are deduplicated by channel and message timestamp.
What can Floqer see regardless of configuration?
- Channel directory. The name, ID, member count, and privacy flag of every public channel and of the private channels the bot is in, so the pickers can list them. This is metadata only.
- Workspace details. The workspace ID, name, and domain.
- User profiles. The name, title, and email of a user, read only when that user authored an imported message, and cached for one hour.
How long is data retained, and what is it used for?
Floqer keeps data from Slack for the duration of your engagement, so workflows can operate on the rows and re-runs stay consistent. It is held in Floqer's managed cloud infrastructure, scoped to your organization. Floqer never sells or licenses it, never uses it to train or evaluate models, and never offers it to other customers.
How is data deleted?
You can delete lists, workflows, and connections in the product at any time. For full deletion, write to privacy@floqer.com. Deletion covers rows ingested from Slack, workflow data derived from them, stored files, and the connection's credentials, and completes within 30 days with written confirmation.
If you have a question this page does not answer, contact hello@floqer.com.