Connect to Slack
Query the Ascend Gateway V5 directly from Slack by messaging the Ascend GTM bot.
:::info Requirements
- Ascend GTM Slack bot installed in your workspace
- Bot must have
chat:write,im:history, andim:readscopes :::
How It Works
DM the Ascend GTM bot in Slack. The bot receives your message, executes the appropriate V5 gateway call, and replies with the results.
You: "list my connected APIs"
Bot: 📡 Connected Providers (53):
✅ hubspot (CRM)
✅ google_ads (Advertising)
✅ salesforce (CRM)
✅ ga4 (Analytics)
... and 49 more
Supported Queries
| Query Pattern | What It Does |
|---|---|
| "list APIs" / "show providers" / "what's connected" | Lists all connected API providers |
| "hubspot contacts" / "search contacts" | Searches HubSpot CRM |
| "google ads" / "campaigns" | Queries Google Ads |
| "health" / "status" | Shows gateway health status |
| "help" | Shows available commands |
Example Conversations
Check System Health
You: "How's the gateway?"
Bot: 🟢 Gateway Healthy
Tokens: 42 active, 0 expired
Errors (1h): 0
Providers: 64 configured
Search CRM
You: "Find HubSpot contacts from this week"
Bot: 📋 HubSpot Contacts (5 results):
• John Smith (john@example.com) — Created 2026-04-10
• Jane Doe (jane@company.com) — Created 2026-04-09
...
Setup (Workspace Admin)
If the bot is not yet installed:
- Go to api.slack.com/apps → select the Ascend GTM app
- Under OAuth & Permissions, ensure these scopes are granted:
chat:write— Send messagesim:history— Read DM historyim:read— Detect DM channels
- Under Event Subscriptions, set the Request URL to:
https://ascend-gateway-v5.ascendgtm.workers.dev/slack/events
- Subscribe to:
message.im(Direct messages) - Install/reinstall the app to the workspace
Limitations
- DMs only — the bot responds to direct messages, not channel mentions (for security)
- Text queries — no file uploads or Slack-specific formatting in queries
- Default tenant — Slack queries use the
ascendtenant. Multi-tenant Slack is a future feature. - No scheduling (yet) — scheduling intent detection is built but calendar integration is Phase 2
Troubleshooting
| Issue | Fix |
|---|---|
| Bot doesn't respond | Check bot has chat:write scope |
| "Invalid signature" in logs | Verify SLACK_SIGNING_SECRET in Wrangler secrets |
| Results truncated | Large results are trimmed to fit Slack's 3000-char block limit |