Slack
Askel connects to each customer's Slack workspace once. Your product can post messages, read channel history, and react to events without your team writing or maintaining per-customer Slack integration code.
What you can do
Post messages to channels and DMs
Send formatted messages, blocks, and attachments to public or private channels, plus direct messages to individual workspace members.
Read channel history
Fetch recent messages from a channel using conversations.history, useful for summarising activity, detecting keywords, or building digests.
React to events via webhooks
Subscribe to message events, app mentions, reactions, and channel membership changes. Askel routes incoming events to your workflow logic.
Look up users and channels
Resolve a user's display name, email, or channel ID from the workspace directory. Useful for routing notifications to the right destination.
Upload files and snippets
Post CSV exports, PDF reports, or code snippets directly into a Slack channel using the files.upload API method.
Audit every message sent
Askel logs every Slack API call with the channel ID, message payload, timestamp, and response. Your team can inspect or replay any outbound message.
Sending onboarding status updates to a customer's Slack channel
You sell a customer-data platform. Fenwick Labs wants onboarding progress posted into their internal #onboarding-status channel as each step completes, so their ops team can see real-time progress without leaving Slack.
- 1
Connect once
Fenwick's workspace admin clicks Connect Slack inside your product. Slack's OAuth consent screen lists the requested scopes, and the admin approves. Askel stores the access token and handles refresh.
- 2
Identify the target channel
Askel calls conversations.list to enumerate channels the integration can reach. Your product lets Fenwick pick #onboarding-status from a dropdown.
- 3
Configure the trigger
Your team maps each onboarding milestone to a Slack message template. When a milestone completes in your product, the corresponding message is queued.
- 4
Post the first message
The moment Fenwick's data pipeline completes its first sync, your product triggers the workflow. Askel posts a formatted update to #onboarding-status with a summary and next steps.
- 5
Monitor delivery
Askel logs every send with the channel ID, timestamp, and Slack's response. If a scope is revoked or the channel is archived, the workflow pauses and your team is notified.
OAuth 2.0
Customer's workspace admin clicks Connect Slack and approves the requested scopes on Slack's OAuth consent screen. Askel stores the access token and refreshes it automatically. No tokens, client IDs, or secrets touch your codebase, and the scope set is bounded to what your workflows actually need.
How Askel sits between your product and the customer's system
FAQ for Slack
Which Slack plans are supported?+
What scopes does Askel request during OAuth?+
Can we post to private channels?+
What happens if the workspace admin revokes the token?+
catching drift before it breaks, and hitting go-live dates.
© 2025 Askel.ai. All rights reserved.