Connect Agent mail to Clockify

When something happens in Agent mail, 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

Build an automation Browse examples

Examples

Ways Notis can move work from Agent mail to Clockify

View example

Create a Clockify client from an emailed request

Turn an incoming request to add a client into a Clockify client record, using the workspace and client details supplied in the email.

View example

Find Clockify clients requested by email

When an email asks for the clients in a specific Clockify workspace, retrieve that workspace's client list for the run.

View example

Get a Clockify workspace overview on demand

Start a webhook run to retrieve the Clockify workspaces available to the authenticated user.

View example

Refresh the Clockify workspace member list

On a schedule, retrieve the users in a specified Clockify workspace for a current membership reference.

View example

Look up Clockify users by criteria on demand

Start a webhook run to retrieve a paginated, sortable list of workspace users matching the criteria supplied for the lookup.

View example

Review Clockify workspace holidays on a schedule

Retrieve the holidays configured for a Clockify workspace on a recurring schedule for review.

View example

Check a Clockify user's holidays for a period

Use a webhook run to retrieve holidays assigned to a specified user during a supplied date period.

View example

Retrieve Clockify workspace details from an email request

When an incoming email asks for workspace details and identifies the workspace, retrieve its Clockify information.

Supported Triggers and Actions

Notis builds workflows that link Agent mail to Clockify. A trigger fires from one place; an action lands in another.

Agent mail triggers

Clockify actions

Recurring trigger

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

TriggerScheduled

Create Client

Tool to add a new client to a workspace. use when you need to create a client in a specific workspace.

ActionInstant

Webhook trigger

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

TriggerInstant

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.

ActionInstant

New Email Received

Trigger for new emails in an AgentMail inbox

TriggerPolling

Delete Client

Tool to delete a client from a workspace. use after archiving the client and confirming no associated data exists.

ActionInstant

Delete Webhook

Tool to delete a webhook from a workspace. use when you need to remove an existing webhook by its id.

ActionInstant

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.

ActionInstant

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."

ActionInstant

Find User's Team Managers

Tool to get managers of a user in a workspace. use after confirming workspace and user ids are correct.

ActionInstant

Generate New Webhook Token

Tool to generate a new webhook token. use after confirming workspace and webhook ids.

ActionInstant

Trigger Types

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.

New Notion pageStripe chargeCalendar event

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.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

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.

Row insertedValue > limitQuery match

Why AI automation

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.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

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:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

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.