Keep Clockify webhook checks near Jira changes
Make an integration check easier to remember. Ask Notis to retrieve a specified Clockify webhook's details when a Jira issue changes.
Trigger
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.
Action
Get Webhook By ID
Tool to get details of a specific webhook. use after confirming workspace and webhook id.
Why this helps
Integration details are easy to forget to review when project work changes in another tool.
- Bring webhook details into an existing change report
- Reduce manual integration checks
- Keep operational context in a chosen channel
Setup
Build it in a few focused steps.
- 1Connect Jira and Clockify once in the Notis portal.
- 2Create an automation in the portal or tell Notis from any channel.
- 3Ask Notis to retrieve a Clockify webhook by its confirmed id when a Jira issue changes and summarize the details.
- 4Select Jira's Updated Issue trigger for the configured project and choose where run reports should go.
- 5Test with one real issue update and review the correct webhook details.
Questions about this workflow
What information is required?
Confirm the Clockify workspace id and webhook id.
Does this create or change the webhook?
No. It gets details for a specific existing webhook.
Will comments trigger this check?
No. Jira's Updated Issue event does not fire on comment activity.
When this happens · Trigger
Do this · Action
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.
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.