Weekly launch status from Linear in Slack
Every Friday, the agent reads your in-progress Linear projects and posts a plain-English status to #launches for the marketing team.
Letaido's Linear integrations let an AI agent read and create issues and projects, and act on them in 64 other apps.
Launches, requests and fixes passed between teams, each checked step by step. Open one to watch it run.
Every Friday, the agent reads your in-progress Linear projects and posts a plain-English status to #launches for the marketing team.
Describe a launch in chat and the agent sets it up in Linear: a project and one issue per task, with owners and due dates.
When a Linear issue that customers asked for is marked Done, the agent builds a HubSpot list of those customers' contacts for your launch email.
Each new Notion marketing request becomes a Linear issue for the design team, and the issue link goes back on the Notion row.
Every Monday, the agent turns critical Ahrefs Site Audit errors into Linear issues for your web team, skipping any already open.
Every Friday, the agent turns the Linear issues your product team finished that week into customer-facing release notes in a Google Doc.
Six ways to connect Linear, and where each one fits.
| Option | Set up by asking | Works across your apps | Runs on its own | No code | Connects thousands of apps |
|---|---|---|---|---|---|
| Yes | Yes | Yes | Yes | No | |
| Linear's integration directory | No | Partly | Yes | Yes | Partly |
| Linear Agent | Yes | Partly | Partly | Yes | No |
| Zapier and similar | No | Yes | Yes | Partly | Yes |
| Linear API and webhooks | No | Partly | Partly | No | Partly |
| Linear MCP server | Partly | Partly | Partly | Partly | Partly |
| Option | How it works | Best for | Watch out for |
|---|---|---|---|
| Letaido AI agent | You describe the job. The agent reads and writes issues, projects and customer requests and uses 64 other apps, on a schedule, on a Linear event or when you ask. | Marketing work that follows product work: launch status, release notes, customer lists. | 65 apps, not thousands. Event jobs need an admin's API key. |
| Linear's integration directory | Apps built by Linear, such as Slack and GitHub, plus over 250 from third parties. | Linking issues to code, chat and support tickets. | Most need a workspace admin to install. Each does one set job. |
| Linear Agent | Linear's own AI answers questions about your workspace and creates and updates issues and projects, in Linear or from Slack. | Working inside Linear by asking. | Other tools come in through MCP servers an admin connects. |
| Zapier and similar | Triggers such as a new issue, customer or customer request start workflows in other apps. | Fixed handoffs, like a form entry becoming an issue. | You set each step in advance, and it does the same thing every time. |
| Linear API and webhooks | A GraphQL API that reads and changes every entity, and webhooks for changes to issues, projects and more. | In-house tools with exact needs. | Needs developers. Webhooks need an admin. |
| Linear MCP server | Linear's hosted MCP server lets AI apps such as Claude and Cursor find, create and update issues and projects in a chat. | Working on Linear from your AI app. | Runs when you chat. A read-only address is available. |
Connect Linear once. After that, you describe each job in plain English.
Allow all read operations once per app; approve each kind of write once.
Save it to run every Friday or on a Linear change.
A Linear change, a schedule or you asking starts the job.
In Linear, go to Settings, Account, Security and access, and create a personal API key with the access your jobs need.
Only workspace admins can create webhooks. With an admin's key, Letaido creates the webhook and its signing secret itself, so there is nothing to paste into Linear.
Add the key in Letaido. Leave the signing secret empty: Letaido fills it in on the first event job.
Allow all read operations once per app; approve each kind of write once. Then save it to repeat.
27 actions across 9 groups, from issues and projects to customer requests.
Create a personal API key in Linear under Settings, Account, Security and access, and paste it into Letaido. For jobs that start from a Linear change, use a workspace admin's key, because only admins can create webhooks. Letaido then sets up the webhook and its signing secret for you.
New and updated issues, projects, project updates, initiative updates, customers and customer requests, plus new comments: 15 events in all. The job checks the details itself, such as whether an issue just moved to Done.
Yes. Linear hosts an MCP server that AI apps such as Claude and Cursor use to find, create and update issues and projects in a chat, with a read-only address too. Letaido is not an MCP server: it has its own Linear connector and runs whole jobs on a schedule or on a Linear change.
Linear Agent works inside Linear and Slack, and reaches other tools through MCP servers an admin connects. Letaido's agent starts from Linear and finishes the job in your marketing apps, like building a HubSpot list when a requested feature ships.
Yes, once an admin turns on Customer Requests in Linear. The agent reads which customers asked for an issue and their domains, and can match them to HubSpot companies.
Reads and writes follow the key's user, so it sees the private teams that person is in. Event webhooks cover all public teams.
Allow all read operations once per app; approve each kind of write once.
Connect Linear, then ask for a job like "Post a weekly Linear launch status in Slack". Leta gets it done on your schedule, or the moment you ask.
Get LetaidoSearch, filter, and retrieve Linear issues by ID, title, assignee, team, state, label, priority, or date range.
Create new Linear issues and update fields on existing ones.
Add or remove labels on issues and attach external links or resources to them.
Post comments on issues or project updates and list existing comments on an issue.
Create projects, fetch them by ID, list all projects, and read status updates posted to a project.
Create customer records and linked needs/requests, and list existing customers and their needs.
List teams, users, labels, workflow states, cycles, and initiatives available in the workspace.
List Linear documents the authenticated user can access.
Verify the authenticated API key by returning the current viewer account.