When someone reacts with :bug:
Slack bug reports as Linear issues
React with :bug: to a Slack message; Leta files a Linear issue or adds it to a matching one, then replies with the link.
Linear + Slack integration
Combine Linear + Slack and move issues into channels where your team already talks. Just ask Letaido's AI agent and watch it do the work.
Best Linear and Slack integration jobs to start with
Use this Linear Slack integration for bug reports, project updates and customer requests.
When a project update is posted
Plain-English Linear project updates in Slack
When someone posts a Linear project update, Leta rewrites it for marketing and sales and posts it to #launches with health and target date.
When someone mentions Letaido
Customer requests from Slack into Linear
Mention @Letaido with what a customer asked for; Leta logs it as a Linear customer request on the matching issue, so product sees the demand.
Every Friday at 11am
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.
When an issue is marked Done
Tell Slack reporters their issue is marked Done
When a WEB issue is marked Done, Leta replies in each Slack thread where it was reported, so the reporter hears back.
Linear Slack integration options, compared
Linear's own Slack app covers issues and standard notifications. Its optional Linear Agent and Loops add AI actions and scheduled Slack posts, with Loops on paid plans using AI credits.
| Option | Create issues from Slack | Linear updates in Slack | Anyone in Slack can file | Logs customer requests | Rewrites for marketing and sales |
|---|---|---|---|---|---|
 Letaido AI agent | Yes | Yes | Yes | Yes | Yes |
| Linear for Slack, standard notifications | Yes | Yes | No | Yes | No |
| Linear Agent and Loops in Slack | Yes | Yes | Partly | Partly | Partly |
| Linear Asks | Yes | Partly | Yes | Yes | No |
| Zapier | Yes | Yes | Yes | Yes | Partly |
Read the full comparison
| Option | Direction | What starts it | Best for | Watch out for |
|---|---|---|---|---|
| Letaido AI agent | Slack into Linear issues and customer requests, and Linear updates back to Slack | A Slack reaction or mention, a Linear event such as a project update, a schedule, or when you ask | Jobs across teams: bug reports filed with a duplicate check, project updates in plain English, customer requests logged on the right issue, reporters told when an issue is marked Done | Not a feed of every issue change. Linear events need an API key from a workspace admin, and the bot must be invited to each channel |
| Linear for Slack, standard notifications | Both ways: issues from Slack messages, notifications and synced threads back | You using the Create new issue message action, or Linear activity you subscribe a channel to | Creating issues from messages, synced comment threads, team, project and personal notifications, rich link previews | A Linear admin connects it. Only people with a Linear account can create issues from Slack, and standard notifications follow Linear's own format |
| Linear Agent and Loops in Slack | Both ways through Linear's Slack integration: @Linear actions from a conversation, and Loops that read public channels and post to Slack | You mentioning @Linear in Slack, or a Loop on a schedule, on a Linear event or on a new top-level message in a selected public channel | Issues and feature requests from a thread's context, scheduled digests of team work in Slack, user-facing messaging drafted from closed issues | Loops need a paid plan and draw AI credits, and pause when credits run out. An admin must enable Linear Agent and allow Loops access in Slack settings, and Loops work only in public channels |
| Linear Asks | Slack into Linear, with a synced thread back to the requester | Someone using /ask or the message menu in Slack | Request intake from people who don't use Linear, landing in the team's Triage | Needs Linear's Business or Enterprise plan. Private Slack channels and per-channel setup need Enterprise |
| Zapier | Slack into Linear, or Linear into Slack, one recipe at a time | A trigger in one app, such as a new reaction in Slack or an updated issue in Linear | Set recipes such as a Linear issue for each flagged Slack message, or a Slack message for each new issue | Rewriting or summarizing Linear updates for marketing and sales needs an AI step you add and set up in the Zap. Some Slack triggers are polling, every 15 minutes on Zapier's lowest plan |
Linear and Slack: the old way vs. Letaido
- 1Spot the bug report in Slack
- 2Search Linear for a duplicate
- 3Open a new issue
- 4Paste the report and the link
- 5Reply with the issue link
When someone reacts to a Slack message with :bug:, file it for the WEB team in Linear. Go on only when the message has exactly one :bug: at the moment you check its reactions. So if two people add :bug: before that check, the message is skipped, and if someone removes the :bug: and adds it again, it is handled again. Search every page of Linear results for an open WEB issue about the same problem: if one exists, add a comment with the report, who reported it and a link to the Slack message; if not, create a WEB issue with a short title and the same details. Then reply under the message with the issue link. Ignore other reactions.
#marketing, thread in Slack
Logged 2 problems from this message
WEB-198 Start trial button does nothing on iOS, added your report; WEB-231 Pricing toggle shows monthly prices on annual, filed new
How Linear and Slack jobs start
When something happens
A job can start when someone reacts with :bug: in Slack or a project update is posted in Linear or someone mentions @Letaido in Slack or an issue is updated in Linear, like “Slack bug reports as Linear issues”.
On a schedule
Saved as an automation, like “Weekly launch status from Linear in Slack”: every Friday at 11am.
When you ask
One message, 91 Linear and Slack actions to draw on.
How to set up the Linear Slack integration
-
1Paste a Linear API key
-
2Create the Slack app from Letaido's manifest
-
3Approve the first Slack run
Allow all read operations once per app; approve each kind of write once.
-
4Watch the first run in chat
-
5Choose when it runs
Every Linear and Slack action the agent can take
Linear
9 groups: 18 reads, 9 writes
- Manage projects
- Browse workspace directory
- Read documents
- 6 more
Get viewer · List projects · List issue comments · List customers
Slack
10 groups: 27 reads, 37 writes
- Create and edit canvases
- Look up and manage users
- Manage user groups
- 7 more
Get thread messages · List user conversations · Get user · List usergroups
Frequently asked
Does Linear integrate with Slack? +
Yes. Linear's own Slack app creates issues from messages, syncs threads and posts notifications. Letaido's AI agent, Leta, adds jobs on top for marketing, sales and customer success, and the jobs on this page have been checked step by step.
How do I connect Linear and Slack to Letaido? +
Paste a Linear API key and create the Slack app from Letaido's manifest, then invite the Letaido bot to the channels it should use. Then describe the job in chat, or paste a prompt from a job on this page.
Can people without a Linear account file issues from Slack? +
Yes. Anyone in the channel can react with :bug: and Leta files the report in Linear, or adds it to a matching open issue, then replies with the link. With Linear's own app, only people with a Linear account can create issues; Linear Asks needs a Business or Enterprise plan.
Can it send Linear notifications to Slack? +
Yes, for the jobs you set up: a plain-English post when a project update goes up, a weekly launch status every Friday, or a reply in the Slack thread when a reported issue is marked Done. It is not a feed of every issue change.
Do I need a Linear admin for jobs that start on a Linear event? +
Yes. Jobs that start on a Linear event, such as a project update or an issue moving to Done, need an API key from a Linear workspace admin, because only admins can create webhooks. Letaido creates the webhook for you. Reaction and mention jobs need those events switched on in your Slack app.
How is Letaido different from the Linear app for Slack? +
Linear's standard notifications post in Linear's own format. Its optional Linear Agent adds @Linear actions in Slack, and Loops add scheduled or event-driven Slack posts, but Loops need a paid plan, use AI credits and work only in public channels. Leta runs a job you describe across both apps: it checks for a duplicate before filing, logs customer requests on the right issue, and rewrites project updates for marketing and sales.
Will it ask before it posts in Slack or changes Linear? +
Allow all read operations once per app; approve each kind of write once.
Put Linear and Slack to work today
Connect Linear and Slack, then ask for a job like "File Slack messages I flag with :bug: as Linear issues". Leta gets it done the moment something happens, or the moment you ask.
Get Letaido