// Connected app tool recipes for Composio integrations (Gmail, Slack, GitHub, Notion, Google Calendar, Linear)
Manage DuckDB CRM data, aggressive relation-linked fields, and synced markdown documents in the workspace. Use when creating or updating objects, fields, entries, foreign-table links, row notes, or entry-linked edit logs.
Find and connect with engineers working on ELK/observability stacks at ICP companies. Use when: (1) Researching individual contributors at a company that passed ICP company research, (2) Finding engineers with ELK/platform/SRE skills, (3) Verifying someone's work involves ELK/logstash/observability, (4) Connecting with practitioners who manage the stack day-to-day, (5) Discovering new ICP companies through engineer profiles. Workflow: Company from CRM → DuckDuckGo → PinchTab → LinkedIn MCP (verify ELK in skills/experience + connect) → Add to engineers CRM. Flipped discovery: If engineer has strong ELK signals but company isn't in CRM → add company as 'Discovered'. This skill DOES connect on LinkedIn.
Find and connect with team leads/VPs running observability/ELK stacks at ICP companies. Use when: (1) Researching decision-makers at a company that passed ICP company research, (2) Finding VP/Director/Team Lead contacts (VP Platform, Director SRE, Infrastructure Lead), (3) Verifying someone's role includes observability/platform, (4) Connecting with buyers who have budget authority, (5) Discovering new ICP companies through team lead profiles. Workflow: Company from CRM → DuckDuckGo → PinchTab → LinkedIn MCP (verify + connect) → Add to team_leads CRM. Flipped discovery: If team lead runs platform/observability but company isn't in CRM → add company as 'Discovered'. This skill DOES connect on LinkedIn.
Debugging CRM objects not showing entries despite data existing in database
Research companies against ICP criteria for ELK/observability tools. Use when: (1) Finding companies that match ICP (MSSPs, SOC-as-a-service, SIEM providers, cybersecurity where observability IS their product), (2) Evaluating if a company fits the ideal customer profile, (3) Researching company size, business model, and ELK criticality, (4) Building prospect lists for outreach. ICP: Small-medium companies (≤200 employees) where observability/ELK is mission-critical to revenue. Use DuckDuckGo first, then PinchTab for deeper research, then LinkedIn MCP ONLY for company/people lookup (never for outreach).
Browser automation for general web browsing, reading blogs, Googling, and extracting website information. Use PinchTab when you need to interact with websites that don't have dedicated MCP servers. For Reddit tasks, use reddit-mcp. For LinkedIn tasks, use linkedin-mcp - NEVER use PinchTab for LinkedIn. Use PinchTab for: (1) Searching Google and browsing search results, (2) Reading blogs and articles, (3) General web surfing when no dedicated tool exists, (4) Taking screenshots of websites, (5) Extracting text content from pages, (6) Testing websites or debugging web issues.
| name | composio-apps |
| description | Connected app tool recipes for Composio integrations (Gmail, Slack, GitHub, Notion, Google Calendar, Linear) |
Use Composio tools only. In DenchClaw these may already appear directly as tool names like GMAIL_FETCH_EMAILS; call those directly when present.
Do not use:
gogcurl/v1/composio/* gateway callsIf the user mentions Composio, rube, map, MCP, or says an app is already connected, Composio is the only allowed integration path. If the Composio tools are unavailable in the current session, stop and report repair guidance instead of bypassing them.
The workspace may contain composio-tool-index.json with the exact tool names and hints for your connected apps — prefer that file when present. If the exact tool is not obvious, call composio_resolve_tool first to get the correct tool name, argument shape, and default args.
GMAIL_FETCH_EMAILS).gog, curl, or raw gateway HTTP for a connected app task unless the user explicitly asks for that non-Composio path.| Intent | Tool | Defaults / notes |
|---|---|---|
| List / read recent mail | GMAIL_FETCH_EMAILS | label_ids: ["INBOX"], max_results: 10 |
| Read one message | GMAIL_FETCH_MESSAGE_BY_MESSAGE_ID | message_id from list results |
| Send mail | GMAIL_SEND_EMAIL | to, subject, body (use schema field names) |
Gotcha: label_ids must be an array like ["INBOX"], never a single string.
| Intent | Tool | Defaults / notes |
|---|---|---|
| Send a message | SLACK_SEND_MESSAGE | channel, text |
| List channels / DMs | SLACK_LIST_CONVERSATIONS | Use schema filters if needed |
Gotcha: channel is usually a channel ID (often starts with C), not the display name.
| Intent | Tool | Defaults / notes |
|---|---|---|
| List repos for user | GITHUB_LIST_REPOSITORIES_FOR_THE_AUTHENTICATED_USER | Pagination per schema |
| Find / search pull requests | GITHUB_FIND_PULL_REQUESTS | Best first path for "recent PRs" or broad PR search |
| List pull requests in a repo | GITHUB_LIST_PULL_REQUESTS | Requires owner and repo |
| Get one pull request | GITHUB_GET_A_PULL_REQUEST | owner, repo, pull_number |
| Repo metadata | GITHUB_GET_A_REPOSITORY | owner, repo |
| Create issue | GITHUB_CREATE_AN_ISSUE | owner, repo, title, body |
| Intent | Tool | Defaults / notes |
|---|---|---|
| Search | NOTION_SEARCH | Query string per schema |
| Read page | NOTION_GET_PAGE | Page ID |
| Create page | NOTION_CREATE_PAGE | Parent object per schema |
| Intent | Tool | Defaults / notes |
|---|---|---|
| List calendars | GOOGLE_CALENDAR_CALENDAR_LIST | Optional params per schema |
| Upcoming events | GOOGLE_CALENDAR_EVENTS_LIST | Prefer a clear time window when possible |
| List events | GOOGLE_CALENDAR_EVENTS_LIST | calendar_id, time range (time_min / time_max as RFC3339) |
| Find event | GOOGLE_CALENDAR_EVENTS_LIST | Use search text / date window fields supported by the schema |
| Create event | GOOGLE_CALENDAR_CREATE_EVENT | Calendar id + event payload per schema |
Gotcha: Datetimes should be RFC3339 strings.
| Intent | Tool | Defaults / notes |
|---|---|---|
| List issues | LINEAR_LIST_ISSUES | Filters per schema |
| Get issue | LINEAR_GET_ISSUE | Issue id |
| Create issue | LINEAR_CREATE_ISSUE | Team id, title, description per schema |
When delegating, include: which app, the exact tool name, and the argument object you intend (copy shapes from the tool schema, composio_resolve_tool, or composio-tool-index.json).