New Keyword Mention
Receive new human messages containing [Issue] anywhere without case sensitivity, including matching thread replies. Ignore bots; choose channels or leave Channels empty to watch all accessible ones.
Workflow template
Capture Slack messages containing [Issue] as Linear issues. Use the complete message as the title and add author ID, timestamp and a source-channel link in the description.
How it works
Receive new human messages containing [Issue] anywhere without case sensitivity, including matching thread replies. Ignore bots; choose channels or leave Channels empty to watch all accessible ones.
Create an issue in your chosen team with the complete message, including [Issue], as its title. Add author ID, timestamp, channel link and a written instruction to review and assign an owner; no assignee or project is chosen.
The result
[Issue] Review the Bremen onboarding form — Grüße
Captured from Slack Author ID: UEXAMPLE109 Message timestamp: 1789574400.000109 Source channel: https://app.slack.com/client/TEXAMPLE109/CEXAMPLE109 Review the request and assign an owner.
Fictional issue. The marker is retained in the title. Assigning an owner is written guidance, not an automatic assignment; the source URL opens a channel.
Before activation
Connect Slack, choose source channels and add FastHook before activation. Keep [Issue], case-insensitive matching and ignored bots. Review the broad accessible-channel scope if Channels is empty.
Connect Linear and browse to a team where the connection can create issues. Review team access because it will receive copied Slack text. The template selects no project or assignee.
Activate and post a new human message containing [Issue]. Keep it short and plain because the complete text becomes the title. Verify the issue’s title, metadata and channel link, then assign an owner yourself if needed.
The whole message becomes the title. The marker is not stripped, and Slack mentions or formatting are copied as supplied rather than converted. Keep requests short and plain. Files and surrounding thread history are not copied.
The description provides context, not automation. Author ID, timestamp and a channel URL accompany an instruction to review and assign an owner. No assignee, project, comment-sync or status-sync step is configured.
Only new matches create issues. Matching human replies qualify; bots, old messages, edits and deletions do not. Destination team members can read the copied text, and manual reruns may create another issue rather than update the original.
No. The complete Slack message becomes the title, including its marker. Keep messages short and use plain text; Slack mentions and formatting are not converted.
No. You choose the Linear team, but no assignee or project is configured. Review the request and assign an owner is description text for a person to follow.
No. It opens the source channel. Author ID and the original Slack timestamp are included separately in the issue description.
No. This captures new matching human messages or replies only. History, edits, deletions, files and thread history are excluded, and manual reruns can create duplicate issues.