Skip to content
Notis

Turn Clientary project hours into a Linear issue

Capture the work behind a Clientary time entry as a clear Linear issue, without rebuilding the project context by hand.

Trigger

Webhook received

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

Action

Create linear issue

Creates a new issue in a specified linear project and team, requiring a title and description, and allowing for optional properties like assignee, state, priority, cycle, and due date.

Why this helps

Project hours can reveal work that needs follow-up, but copying the details into Linear adds another step where context can get lost.

  • Carry project and time-entry context into Linear.
  • Reduce manual re-entry between client work and issue tracking.
  • Keep follow-up work visible to the team.

Setup

Build it in a few focused steps.

  • 1Connect Clientary and Linear once in the Notis portal.
  • 2Create an automation in Automations, New Automation, or tell Notis in plain language from any channel.
  • 3In one instruction, ask Notis to create a Linear issue from the Clientary project-hours details supplied with the request.
  • 4Pick the webhook trigger and choose where run reports should go.
  • 5Test with one real project-hours example and review the resulting issue.

Questions about this workflow

What starts this automation?

A webhook request starts it. Clientary does not provide a listed trigger event for this workflow.

What project details will the issue include?

Notis can use the details supplied with the webhook request. Include the project, tracked hours, and the work or follow-up that should be captured.

Does the workflow choose a Linear team or project automatically?

The create issue action requires a Linear team and project. Include the intended destination in the instruction or request context, and ensure it is valid in your Linear workspace.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Clientary to Linear. A trigger fires from one place; an action lands in another.

Clientary triggers

Linear actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Create linear attachment

Creates a new attachment and associates it with a specific, existing linear issue.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Create a comment

Creates a new comment on a specified linear issue.

ActionInstant

Create linear issue

Creates a new issue in a specified linear project and team, requiring a title and description, and allowing for optional properties like assignee, state, priority, cycle, and due date.

ActionInstant

Get create issue default params

Fetches a linear team's default issue estimate and state, useful for pre-filling new issue forms.

ActionInstant

Create a label

Creates a new label in linear for a specified team, used to categorize and organize issues.

ActionInstant

Delete issue

Archives an existing linear issue by its id, which is linear's standard way of deleting issues; the operation is idempotent.

ActionInstant

Get all teams

Retrieves all teams from the linear workspace without requiring any parameters.

ActionInstant

Download issue attachments

Downloads a specific attachment from a linear issue; the `file name` must include the correct file extension.

ActionInstant

Connect any two apps with Notis in the middle.

Clientary and Linear, or any other combination from 1,000+ integrations.

When this happens · Trigger

Do this · Action

Save your first hour today.

7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Linear.