Linear Cycle Digest
Emails a digest of the current Linear cycle — its name, end date, progress, and the list of issues (with state and assignee) — to the workflow's InTouch subscribers.
Use case
Linear organizes work into time-boxed cycles (sprints). Run this on a schedule (e.g. every weekday at 9am, or before a planning meeting) to give the team a snapshot of where the active cycle stands without anyone opening Linear.
Required credentials
| Credential | Used by | How to supply |
|---|---|---|
| Linear API key | linear connector (apiKey) |
Create a Linear personal API key (Linear → Settings → Security & access → Personal API keys → New key). Store it as an InTouch credential (or runtime env) and set the task's apiKey property to reference it. The workflow.yaml ships with the placeholder <set via credential> — never hardcode the key. |
Delivery uses the built-in message tool, which notifies the workflow's contacts
(user intouch in notifications), so no separate outbound-messaging
credential is required for delivery. Add at least one contact with a delivery
profile so the digest has somewhere to go.
What it does each run
- fetch (
linearconnector) — callsoperation: issueswith a GraphQL query that pulls the active cycle (isActive: true): itsname,number,endsAt,progress, and the issues in it (identifier, title, state name/type, assignee). The connector publishes exactly two outputs: -{{fetch.result}}— the API response as a JSON string -{{fetch.status}}— the HTTP status code - notify (
messagetool) — emails the workflow's contacts, embedding{{fetch.result}}and{{fetch.status}}in the body.
If the Linear step errors, the notifications block alerts the intouch
user so a failed pull doesn't pass silently.
The
linearconnector publishes onlyresultandstatus. The notify step references only those — it does not assume any per-field outputs like counts or completion percentages.