The moment it happens

Get an email when a Deel contract starts or ends

You hear about new and terminated contracts as they happen, without checking Deel.

Runs: The moment it happens
Apps: Deel
AI: Not needed
Access: contracts:read, webhooks:write

Send this to your assistant

Create a ClickRuntime automation: whenever a contract is created or terminated in Deel, email me the person, the contract type, the country and the effective date.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Add to ChatGPT Add to Claude

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

A fast-growing company with contractors in a dozen countries finds out a contract has ended only when an invoice shows up for work nobody asked for, or when a laptop is never returned. In Deel, contracts are created, signed, amended and terminated by different people, and the finance lead or IT admin is rarely the one clicking the button. The knock-on tasks (account access, equipment, payroll cut-off, final payment) wait on someone remembering to open the Deel contracts list.

As soon as Deel sends an event for a contract being created, changing status or being terminated, an email goes out with a short summary of what happened: which contract, which worker, and the new status. Nothing is polled on a timer, so the note lands within moments of the change and arrives in a mailbox people already read.

It is especially useful for operations and finance teams who need to react to a contract status change but do not work in Deel all day.

What you get out of it

Access removed the day work ends
When a contract is terminated, the email reaches IT or the hiring manager the same day, so logins, shared drives and tool seats are closed while the person is still on the offboarding list, not weeks later when nobody remembers who they were.
No invoices for ended contracts
Finance learns a contract was terminated before the next payment cycle, so a contractor is not paid for a period after the agreement stopped. Recovering money from someone in another country is slow and awkward, and this avoids the conversation entirely.
New hires start with what they need
A created-contract email tells the team a contractor is about to start, which leaves time to prepare equipment, a Slack invite and a project brief before day one. The same message is a cue for the manager to send a welcome note.
A dated record of every status change
Each email is a timestamped note of when a contract moved from one state to another. When an auditor, a lawyer or the worker later asks exactly when an agreement ended, you can search your inbox instead of reconstructing it from memory.
Status changes you did not make get noticed
If someone else on the team amends or ends a contract, you hear about it. That catches mistakes, such as the wrong worker being terminated, while they can still be reversed and before the person has been told anything wrong.

How it works

What happens, step by step

When a contract is created or terminated in Deel, Deel tells ClickRuntime straight away.
ClickRuntime picks out the person, contract type, country and effective date.
You get an email summarising the change, without having to check Deel.

Before it runs live

Connect Deel
Paste your automation's link into the other app's webhook settings

What you get

RunsThe moment it happens

Get an email when a Deel contract starts or endsjust nowSucceeded

Email · New contract: Ana CostaPerson: Ana Costa Type: pay_as_you_go_time_based Country: PT Effective: 2026-11-01

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.

Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

Changes you can ask for

Act only on the items that match your own rules, and skip the rest
Add an AI step, for example to summarize, sort or draft a reply
Add another app, for example also send it to Slack
Combine it with other Deel steps into one automation

Under the hood

The code that runs this automation

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.

contract_changes_alert.pyexample

from clickruntime import on_event, notify

WATCH = {"contract.created": "New contract", "contract.terminated": "Contract terminated"}

@on_event
def handle(event):
    data = (event.json or {}).get("data", {})
    kind = data.get("meta", {}).get("event_type")
    if kind not in WATCH:
        return {"sent": False}
    c = data.get("resource", {})
    who = (c.get("worker") or {}).get("full_name") or c.get("title")
    effective = c.get("termination_date") or c.get("start_date") or ""
    notify.email_me(f"{WATCH[kind]}: {who}",
                    f"Person: {who}\nType: {c.get('type')}\nCountry: {c.get('country') or (c.get('worker') or {}).get('country')}\n"
                    f"Effective: {effective[:10]}")
    return {"sent": True, "event": kind}

FAQ

Common questions

Which Deel contract events can trigger the email?

Deel can notify on contracts being created, signed, changing status and being terminated, and the email is built from whichever event arrives. The summary names the contract and the new status, so you can tell a fresh start from an ending without opening Deel. Events you do not subscribe to never produce an email.

Do I need a particular Deel role to set this up?

Creating a webhook in Deel needs an account with developer or API access, which is usually an organization admin. Once the webhook points at your ClickRuntime URL, ordinary users in Deel do nothing differently, and their normal actions simply start producing emails. The run log keeps each incoming event for checking.

Can the summary go to more than one person?

Yes. The email can be addressed to several recipients, for example finance and IT together. You can also split it so terminations go to the offboarding team while new contracts go to whoever prepares equipment, which keeps each person's inbox limited to the messages they will act on.

What permissions does it need?

contracts:read, webhooks:write. Nothing else in your accounts is used.

Does it need AI?

No. It runs without AI, so it doesn't use your plan's AI allowance.

How many runs does it use?

One run for each event the app sends.

Can I change how it works?

Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

The moment it happens