Skip to content

Starter

Front

Create an issue in Linear when a conversation is closed (archived) in Front

When a conversation is closed (archived) in Front, create an issue in Linear.

Start the 14-day trial, then find it under Templates → Library. It installs into the client you choose, switched off, with its checklist.

Steps
1
Client fills in
1
Accounts
2
Starts
A conversation is closed (archived) in Front, within 5 minutes

UsesBeta

Every step, in order

When it happens in the first app, the step runs in the second, with the client’s own account.

A conversation is closed (archived)
A conversation archived, checked every 5 minutes.
Create an issue
An issue in a team. The output is the new issue: its identifier and link.
  1. Starts whenA conversation is closed (archived)
  2. App stepCreate an issue

What each client fills in

Linear: Team ID
For example the team’s UUID

The accounts it needs

Each is the client’s own, stored encrypted and never copied between clients. Until one is added the client’s checklist shows it, and nothing runs.

  • Front

    In the client’s Front: Settings → Developers → API tokens → Create API token with the Shared resources namespace and the Read and Write permissions (Write for the contact step, Read for the triggers, which list events).

  • In the client’s Linear: Settings → Security & access → Personal API keys → New API key. The triggers make webhooks, which needs a workspace admin’s key.

After you install it

It lands switched off. The client’s checklist holds exactly this:

  1. Connect the client’s Front, for “A conversation is closed (archived)”
  2. Connect the client’s Linear, for “Create an issue”
  3. Fill in Linear: Team ID (For example the team’s UUID)

Thrum is cooking.

Get early access and you’ll be among the first in. Early members get a launch perk.