
Connect
- 404 installs
- 15.6k repo stars
- Updated July 26, 2026
- composiohq/awesome-codex-skills
connect is an agent skill that wires Codex or Claude agents to third-party SaaS APIs and OAuth apps through the Composio CLI for developers who need agents to execute real actions instead of drafting instructions.
About
connect is an AI & Agent Building skill from composiohq/awesome-codex-skills that links Codex or Claude agents to live third-party services via the Composio CLI. Instead of generating text about sending email or creating issues, the skill drives OAuth-connected actions across Gmail, Slack, GitHub, Notion, and 1000+ other services directly from the shell. Developers use it while building agent features that must create records, post messages, or update databases during integration work. Reach for connect when an agent workflow needs authenticated API execution rather than mock responses or manual copy-paste follow-up.
- Composio OAuth and actions
- Agent-to-SaaS bridging
- Codex workflow compatible
- Standardized connector setup
- Reduces bespoke API glue
Connect by the numbers
- 404 all-time installs (skills.sh)
- Ranked #1,961 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/composiohq/awesome-codex-skills --skill connectAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 404 |
|---|---|
| repo stars | ★ 15.6k |
| Last updated | July 26, 2026 |
| Repository | composiohq/awesome-codex-skills ↗ |
How do you connect coding agents to live SaaS APIs?
Wire Codex or Claude agents to third-party SaaS APIs and OAuth apps using Composio Connect during feature integration and live action execution.
Who is it for?
Developers building agent workflows that must send email, create issues, post Slack messages, or update external databases in real time.
Skip if: Teams that only need static API documentation or local-only scripts with no OAuth-connected third-party execution.
When should I use this skill?
A developer wants Codex or Claude to perform live Gmail, Slack, GitHub, Notion, or other SaaS actions through Composio CLI instead of describing steps.
What you get
OAuth-linked Composio CLI sessions and executed third-party API actions from the terminal
- OAuth-connected agent sessions
- Executed third-party API actions
By the numbers
- Connects agents to 1000+ third-party services via Composio CLI
Files
Connect
Connect Codex to any app using the Composio CLI. Stop generating text about what you could do - actually do it from the shell.
When to Use This Skill
Use this skill when you need Codex to:
- Send that email instead of drafting it
- Create that issue instead of describing it
- Post that message instead of suggesting it
- Update that database instead of explaining how
What Changes
| Without Connect | With Connect |
|---|---|
| "Here's a draft email..." | Sends the email |
| "You should create an issue..." | Creates the issue |
| "Post this to Slack..." | Posts it |
| "Add this to Notion..." | Adds it |
Supported Apps
1000+ integrations including:
- Email: Gmail, Outlook, SendGrid
- Chat: Slack, Discord, Teams, Telegram
- Dev: GitHub, GitLab, Jira, Linear
- Docs: Notion, Google Docs, Confluence
- Data: Sheets, Airtable, PostgreSQL
- CRM: HubSpot, Salesforce, Pipedrive
- Storage: Drive, Dropbox, S3
- Social: Twitter, LinkedIn, Reddit
Setup
1. Install the Composio CLI
curl -fsSL https://composio.dev/install | bash2. Log In
composio login
composio whoamiThis opens a browser for authentication and lets you pick your default org and project. Use -y to skip prompts in automated flows.
3. Link the Toolkits You Need
composio link github
composio link gmail
composio link slackEach command walks through OAuth once, then the connection persists.
Done. Codex can now drive any connected app from the shell.
Core Workflow
1. Know the tool slug? → composio execute 2. Don't know the slug? → composio search 3. Need clarification on inputs? → composio execute --get-schema or --dry-run 4. Toolkit not connected? → composio link <toolkit> and retry 5. Multiple steps needed? → composio run for workflows, composio proxy for raw API calls
Examples
Discover a Tool
composio search "create a github issue"
composio search "send an email" --toolkits gmailInspect Inputs Before Calling
composio tools info GITHUB_CREATE_ISSUE
composio execute GITHUB_CREATE_ISSUE --get-schema
composio execute GITHUB_CREATE_ISSUE --dry-run -d '{"owner":"acme","repo":"app","title":"Bug"}'Send an Email
composio execute GMAIL_SEND_EMAIL -d '{
"recipient_email": "sarah@acme.com",
"subject": "Shipped!",
"body": "v2.0 is live, let me know if issues"
}'Create a GitHub Issue
composio execute GITHUB_CREATE_ISSUE -d '{
"owner": "my-org",
"repo": "repo",
"title": "Mobile timeout bug",
"labels": ["bug"]
}'Post to Slack
composio execute SLACK_SEND_MESSAGE -d '{
"channel": "engineering",
"text": "Deploy complete - v2.4.0 live"
}'Run Calls in Parallel
composio execute --parallel \
GMAIL_FETCH_EMAILS -d '{"max_results": 2}' \
GITHUB_GET_THE_AUTHENTICATED_USER -d '{}'Chain Actions with composio run
composio run '
const issues = await search("github issues labeled bug this week");
const summary = issues.map(i => `- ${i.title}`).join("\n");
await execute("SLACK_SEND_MESSAGE", {
channel: "bugs",
text: `This week’s bugs:\n${summary}`
});
'Load reusable workflows from a file:
composio run --file ./workflow.ts -- --repo composiohq/composioRaw API Access (proxy)
When no dedicated tool exists, hit the authenticated API directly:
composio proxy https://gmail.googleapis.com/gmail/v1/users/me/profile \
--toolkit gmail
composio proxy https://gmail.googleapis.com/gmail/v1/users/me/drafts \
--toolkit gmail -X POST -H 'content-type: application/json' \
-d '{"message":{"raw":"..."}}'How It Works
1. You ask Codex to do something 2. Codex picks a slug via composio search or prior knowledge 3. CLI checks connection, prompts composio link if missing 4. Action executes against the real API and returns JSON to stdout
Configuration
Global flags:
--log-level <all|trace|debug|info|warning|error|fatal|none>--helpfor per-command docs
Environment variables:
COMPOSIO_API_KEY- auth credential (set for non-interactive use)COMPOSIO_BASE_URL- custom API endpointCOMPOSIO_SESSION_DIR- override artifact storageCOMPOSIO_DISABLE_TELEMETRY=true- opt out of telemetry
Type-Safe SDK (Optional)
Generate typed client code when you want to call tools from an app rather than the shell:
composio generate ts # TypeScript types
composio generate py # Python typesFlags: -o <dir>, --toolkits <list>, --compact, --transpiled, --type-tools.
Troubleshooting
- `Not logged in` → run
composio login - `Connection required for <toolkit>` → run
composio link <toolkit> - Unknown slug →
composio search "<what you want>"orcomposio tools list <toolkit> - Bad inputs →
composio execute <SLUG> --get-schemathen--dry-run - Action failed → check permissions in the target app
Full reference: docs.composio.dev/docs/cli
---
<p align="center"> <b>Join 20,000+ developers building agents that ship</b> </p>
<p align="center"> <a href="https://platform.composio.dev/?utm_source=Github&utm_content=AwesomeSkills"> <img src="https://img.shields.io/badge/Get_Started_Free-4F46E5?style=for-the-badge" alt="Get Started"/> </a> </p>
Related skills
How it compares
Pick connect when an agent must perform authenticated live SaaS actions; use API doc or schema skills when you only need reference material without OAuth execution.
FAQ
What services does the connect skill support through Composio?
The connect skill uses the Composio CLI to link Codex or Claude agents to Gmail, Slack, GitHub, Notion, and more than 1000 other third-party services. OAuth authentication enables agents to send email, create issues, post messages, and update databases from the terminal.
How is connect different from asking an agent to draft an email or issue?
connect drives authenticated Composio CLI actions that execute against live APIs instead of producing text instructions. A developer gets sent email, created GitHub issues, or updated Notion records without manually completing each step after the agent responds.