LeoYeAI/agent-master-skills / skills/api-gateway
api-gateway
VerifiedConnect to 100+ APIs (Google Workspace, Microsoft 365, GitHub, Notion, Slack, Airtable, HubSpot, etc.) with managed OAuth. Use this skill when users want to interact with external services. Security: The MATON_API_KEY authenticates with Maton.ai but grants NO access to third-party services by itself. Each service requires explicit OAuth authorization by the user through Maton's connect flow. Access is strictly scoped to connections the user has authorized. Provided by Maton (https://maton.ai).
references/slack/README.md
View on GitHub# Slack Routing Reference
**App name:** `slack`
**Base URL proxied:** `slack.com`
## API Path Pattern
```
/slack/api/{method}
```
## Authentication
### Auth Test
```bash
GET /slack/api/auth.test
```
Returns current user and team info.
---
## Messages
### Post Message
```bash
POST /slack/api/chat.postMessage
Content-Type: application/json
{
"channel": "C0123456789",
"text": "Hello, world!"
}
```
With blocks:
```bash
POST /slack/api/chat.postMessage
Content-Type: application/json
{
"channel": "C0123456789",
"blocks": [
{"type": "section", "text": {"type": "mrkdwn", "text": "*Bold* and _italic_"}}
]
}
```
### Post Thread Reply
```bash
POST /slack/api/chat.postMessage
Content-Type: application/json
{
"channel": "C0123456789",
"thread_ts": "1234567890.123456",
"text": "This is a reply in a thread"
}
```
### Update Message
```bash
POST /slack/api/chat.update
Content-Type: application/json
{
"channel": "C0123456789",
"ts": "1234567890.123456",
"text": "Updated message"
}
```
### Delete Message
```bash
POST /slack/api/chat.delete
Content-Type: application/json
{
"channel": "C0123456789",
"ts": "1234567890.123456"
}
```
### Schedule Message
```bash
POST /slack/api/chat.scheduleMessage
Content-Type: application/json
{
"channel": "C0123456789",
"text": "Scheduled message",
"post_at": 1734567890
}
```
### List Scheduled Messages
```bash
GET /slack/api/chat.scheduledMessages.list
```
### Delete Scheduled Message
```bash
POST /slack/api/chat.deleteScheduledMessage
Content-Type: application/json
{
"channel": "C0123456789",
"scheduled_message_id": "Q1234567890"
}
```
### Get Permalink
```bash
GET /slack/api/chat.getPermalink?channel=C0123456789&message_ts=1234567890.123456
```
---
## Conversations (Channels)
### List Channels
```bash
GET /slack/api/conversations.list?types=public_channel,private_channel&limit=100
```
Types: `public_channel`, `private_channel`, `im`, `mpim`
### Get Channel Info
```bash
GET /slack/api/conversations.info?channel=C0123456789
```
### Get Channel History
```bash
GET /slack/api/conversations.history?channel=C0123456789&limit=100
```
With time range:
```bash
GET /slack/api/conversations.history?channel=C0123456789&oldest=1234567890&latest=1234567899
```
### Get Thread Replies
```bash
GET /slack/api/conversations.replies?channel=C0123456789&ts=1234567890.123456
```
### Get Channel Members
```bash
GET /slack/api/conversations.members?channel=C0123456789&limit=100
```
### Create Channel
```bash
POST /slack/api/conversations.create
Content-Type: application/json
{
"name": "new-channel-name",
"is_private": false
}
```
### Join Channel
```bash
POST /slack/api/conversations.join
Content-Type: application/json
{
"channel": "C0123456789"
}
```
### Leave Channel
```bash
POST /slack/api/conversations.leave
Content-Type: application/json
{
"channel": "C0123456789"
}
```
### Archive Channel
```bash
POST /slack/api/conversations.archive
Content-Type: application/json
{
"channel": "C0123456789"
}
```
### Unarchive Channel
```bash
POST /slack/api/conversations.unarchive
Content-Type: application/json
{
"channel": "C0123456789"
}
```
### Rename Channel
```bash
POST /slack/api/conversations.rename
Content-Type: application/json
{
"channel": "C0123456789",
"name": "new-name"
}
```
### Set Channel Topic
```bash
POST /slack/api/conversations.setTopic
Content-Type: application/json
{
"channel": "C0123456789",
"topic": "Channel topic here"
}
```
### Set Channel Purpose
```bash
POST /slack/api/conversations.setPurpose
Content-Type: application/json
{
"channel": "C0123456789",
"purpose": "Channel purpose here"
}
```
### Invite to Channel
```bash
POST /slack/api/conversations.invite
Content-Type: application/json
{
"channel": "C0123456789",
"users": "U0123456789,U9876543210"
}
```
### Kick from Channel
```bash
POST /slack/api/conversations.kick
Content-Type: application/json
{
"channel": "C0123456789",
"user": "U0123456789"
}
```
### Mark Channel Read
```bash
POST /slack/api/conversations.mark
Content-Type: application/json
{
"channel": "C0123456789",
"ts": "1234567890.123456"
}
```
---
## Direct Messages
### Open DM Conversation
```bash
POST /slack/api/conversations.open
Content-Type: application/json
{
"users": "U0123456789"
}
```
For group DM:
```bash
POST /slack/api/conversations.open
Content-Type: application/json
{
"users": "U0123456789,U9876543210"
}
```
### List DM Channels
```bash
GET /slack/api/conversations.list?types=im
```
### List Group DM Channels
```bash
GET /slack/api/conversations.list?types=mpim
```
### My Conversations
```bash
GET /slack/api/users.conversations?limit=100
```
---
## Users
### List Users
```bash
GET /slack/api/users.list?limit=100
```
### Get User Info
```bash
GET /slack/api/users.info?user=U0123456789
```
### Get User Presence
```bash
GET /slack/api/users.getPresence?user=U0123456789
```
### Set User Presence
```bash
POST /slack/api/users.setPresence
Content-Type: application/json
{
"presence": "away"
}
```
### Lookup User by Email
```bash
GET /slack/api/users.lookupByEmail?email=user@example.com
```
---
## Reactions
### Add Reaction
```bash
POST /slack/api/reactions.add
Content-Type: application/json
{
"channel": "C0123456789",
"name": "thumbsup",
"timestamp": "1234567890.123456"
}
```
### Remove Reaction
```bash
POST /slack/api/reactions.remove
Content-Type: application/json
{
"channel": "C0123456789",
"name": "thumbsup",
"timestamp": "1234567890.123456"
}
```
### Get Reactions on Message
```bash
GET /slack/api/reactions.get?channel=C0123456789×tamp=1234567890.123456
```
### List My Reactions
```bash
GET /slack/api/reactions.list?limit=100
```
---
## Stars
### List Stars
```bash
GET /slack/api/stars.list?limit=100
```
### Add Star
```bash
POST /slack/api/stars.add
Content-Type: application/json
{
"channel": "C0123456789",
"timestamp": "1234567890.123456"
}
```
### Remove Star
```bash
POST /slack/api/stars.remove
Content-Type: application/json
{
"channel": "C0123456789",
"timestamp": "1234567890.123456"
}
```
---
## Bots
### Get Bot Info
```bash
GET /slack/api/bots.info?bot=B0123456789
```
---
## Files
### Upload File
```bash
POST /slack/api/files.upload
Content-Type: multipart/form-data
channels=C0123456789
content=file content here
filename=example.txt
title=Example File
```
### Upload File v2 (Get Upload URL)
```bash
GET /slack/api/files.getUploadURLExternal?filename=example.txt&length=1024
```
### Complete File Upload
```bash
POST /slack/api/files.completeUploadExternal
Content-Type: application/json
{
"files": [{"id": "F0123456789", "title": "My File"}],
"channel_id": "C0123456789"
}
```
### Delete File
```bash
POST /slack/api/files.delete
Content-Type: application/json
{
"file": "F0123456789"
}
```
### Get File Info
```bash
GET /slack/api/files.info?file=F0123456789
```
---
## Notes
- Authentication is automatic via managed OAuth
- Channel IDs: `C` (public), `G` (private/group), `D` (DM)
- User IDs start with `U`, Bot IDs start with `B`, Team IDs start with `T`
- Message timestamps (`ts`) are unique identifiers
- Use `mrkdwn` type for Slack-flavored markdown
- Thread replies use `thread_ts` to reference parent message
- Cursor-based pagination: use `cursor` from `response_metadata.next_cursor`
- If you encounter `missing_scope` errors, contact [Maton Support](mailto:support@maton.ai) to request additional scopes
## Resources
- [Slack API Methods](https://api.slack.com/methods)
- [Web API Reference](https://api.slack.com/web)
- [Block Kit Reference](https://api.slack.com/reference/block-kit)
- [Message Formatting](https://api.slack.com/reference/surfaces/formatting)
- [Rate Limits](https://api.slack.com/docs/rate-limits)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |