OpenWorker Integrations Guide

Permissions: Read channels, post messages, react to threads

OpenWorker reads Slack messages, drafts replies, triages alerts, and posts updates on your behalf. Set a trigger on @mentions to auto-triage incoming requests. The agent pulls thread context before drafting a response, so replies are informed by the full conversation history.

Permissions: Read emails, compose drafts, send messages

OpenWorker scans your inbox, categorizes emails by urgency, drafts replies, and composes new messages. It understands email threads and can reference attachments. Use it to batch-process newsletter unsubscribes, draft meeting follow-ups, or summarize daily correspondence into a digest.

Permissions: Read events, create events, modify events

OpenWorker analyzes your calendar for conflicts, suggests reschedule windows, creates meeting agendas, and blocks focus time. It can cross-reference your calendar with email to prepare briefing docs before important meetings. The agent understands recurring patterns and suggests optimizations.

Permissions: Read repos, issues, PRs; comment on issues

OpenWorker reviews pull request diffs, generates PR summaries, triages new issues by label and priority, and compiles weekly development activity reports. It can cross-reference issues with Slack discussions to provide context when triaging. Perfect for engineering leads managing multiple repositories.

Permissions: Read pages, create pages, update content

OpenWorker reads Notion databases and pages to pull context for reports, creates new documentation pages from templates, and updates existing docs with fresh data. Use it to auto-generate meeting notes pages, update project status trackers, or compile information from multiple Notion databases into a summary.

Permissions: Read files, create documents, update sheets

OpenWorker accesses your Google Drive to read documents, spreadsheets, and presentations for context. It can create new documents from scratch, update spreadsheet data, and compile information from multiple files into a single report. Particularly powerful combined with Gmail for processing email attachments.

Permissions: Read mail, send mail, manage calendar

The Microsoft 365 integration gives OpenWorker access to both Outlook email and calendar through a single OAuth connection. It handles the same email and calendar workflows as the Google equivalents but through the Microsoft ecosystem. Essential for enterprise teams standardized on Microsoft 365.

Permissions: Read contacts, deals, companies; update records

OpenWorker pulls customer data from HubSpot to prepare meeting briefs, generates deal pipeline summaries, and updates contact records after interactions. Sales teams use it to compile account histories before renewal calls, identify deals at risk based on activity patterns, and draft follow-up emails with CRM context.

Permissions: Read issues, update status, add comments

OpenWorker reads Jira boards, triages incoming tickets, updates issue statuses, and generates sprint reports. It can cross-reference Jira issues with Slack conversations and GitHub PRs to provide full context when reporting on project progress. Particularly useful for scrum masters and project managers.

Permissions: Read issues, create issues, update status

For teams using Linear instead of Jira, OpenWorker provides the same project management automation. It triages new issues, assigns priorities based on labels and team workload, and generates cycle reports. The cleaner Linear API often results in faster OpenWorker responses compared to Jira.