Composio Integrations
Connect third-party services — Slack, Gmail, Google Calendar, GitHub, and more — to Tulsk via Composio. Once connected, Ema and agents can use these tools directly in chat and task workflows.
What You Can Connect
Post scheduled reports, answer @Ema mentions in channels, and get alert pings.
Send report emails, draft replies, and let agents triage inbox items.
📧GmailSchedule meetings from chat, show upcoming events in briefings.
📅Google CalendarOpen PRs, comment on issues, and link commits to tasks.
🐙GitHubAnd many more via Composio’s full app catalog — Notion, Linear, Jira, Airtable, HubSpot, Zendesk, and others. The entire enabled catalog is browsable in the UI; apps that don’t yet support one-click connection are shown but greyed out as unavailable.
Connecting a Service
Open Integrations
Go to the sidebar and click Integrations.
Browse the Catalog
The page lists all connectable services with their current state (Connected / Not Connected).
Click Connect
You’ll be redirected through Composio’s OAuth flow to the service’s sign-in page.
Grant Permissions
Authorize the specific scopes needed. Tulsk only requests the minimum for each integration.
Back to Tulsk
On return, the service shows as Connected with your account handle. Ema and agents can now use it.
Using Integrations
Once connected, integrations surface in a few places:
In Ema Chat
Ask Ema to do something with the service:
- “Post a summary of today’s completed tasks to #engineering.”
- “Email the Q1 retro to the leadership@ list.”
- “Schedule a 30-min review with Priya for tomorrow at 2pm.”
In Scheduled Reports
When creating an Ema schedule, pick Slack or Gmail as the delivery channel. See Ema → Scheduled Reports.
In Agent Runs
Agents with the relevant skills enabled can call integration tools directly during a run — e.g. a “Customer Support Agent” can read Zendesk tickets and reply with Gmail.
Integration tools are scoped to your connection. Each user authenticates separately — agents run as the user who triggered them.
Disconnecting
From the Integrations page, click Disconnect on any connected service. This:
- Revokes the OAuth token on Composio’s side.
- Removes the delivery channel from any Ema schedules using it (the schedule keeps running with the remaining channels).
- Does not delete historical deliveries or comments posted via the integration.
Troubleshooting
| Symptom | Likely Cause | Fix |
|---|---|---|
| ”Integration disconnected” error on a schedule run | OAuth token expired or revoked | Reconnect from the Integrations page. |
| Service shows but can’t connect | App is in the catalog but doesn’t yet support one-click connection | Email support — we enable connection for services on request. |
| Duplicate delivery | Webhook retried after success | Harmless; Tulsk deduplicates on the receiving end. |
If a schedule fails to deliver to a specific channel, the run is still logged and the failure surfaces in the Schedule’s run history with the exact error.