Connect Jira to Clockify
When something happens in Jira, Notis takes the next step in Clockify. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Jira to Clockify
Create a Clockify client for each new Jira project
When a Jira project is created, add a matching client in Clockify so project work has a ready client record.
Create Clockify clients with Jira launch context
Create a Clockify client for each new Jira project and include launch context you provide so the record is useful from day one.
Check Clockify clients when a Jira project starts
When a Jira project is created, check existing Clockify clients so you can see whether a matching record already exists.
Pair a new Jira project with a Clockify client
Create a Clockify client when Jira adds a project, linking project setup across the two tools.
Bring Clockify client context into new Jira issue triage
When Jira creates an issue, retrieve Clockify clients and include the client list in a report for quick context.
Refresh client context when Jira issues change
When an issue is updated in the configured Jira project, fetch Clockify clients to include current client context in a report.
Check Clockify workspace membership for new Jira issues
When a Jira issue is created, retrieve Clockify workspace users and share a team visibility report for follow-up.
Share Clockify workspace membership at Jira project kickoff
When Jira adds a project, retrieve Clockify workspace users and send a concise kickoff visibility report.
Review Clockify users after Jira issue updates
When a Jira issue changes, filter Clockify workspace users using criteria in your instruction and share the matching list.
Supported Triggers and Actions
Notis builds workflows that link Jira to Clockify. A trigger fires from one place; an action lands in another.
Jira triggers
Clockify actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Client
Tool to add a new client to a workspace. use when you need to create a client in a specific workspace.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Webhook
Tool to create a new webhook in a workspace. use when you want to subscribe to workspace events by registering a callback url.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Delete Client
Tool to delete a client from a workspace. use after archiving the client and confirming no associated data exists.
New Project
Triggered when a new project is added in Jira
Delete Webhook
Tool to delete a webhook from a workspace. use when you need to remove an existing webhook by its id.
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Filter Workspace Users
Tool to filter users in a workspace by advanced criteria. use when you need a paginated, sortable list of workspace users matching multiple filters.
Find All Users On Workspace
Tool to list all users in a workspace. use when you need to retrieve workspace members after confirming the workspace id. example: "find all users on workspace 64a687e29ae1f428e7ebe303."
Find User's Team Managers
Tool to get managers of a user in a workspace. use after confirming workspace and user ids are correct.
Generate New Webhook Token
Tool to generate a new webhook token. use after confirming workspace and webhook ids.
Four ways to start an automation.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.
Webhook triggers
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
Database triggers
Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.
Classic automation breaks. AI adapts.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Describe it. Notis builds it.
Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.
You · in the Notis Builder
NEW“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”
Notis built this automation:
Watch every run.
Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Jira and Clockify
Connect any two apps with Notis in the middle.
Jira and Clockify, 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 Clockify.