The moment it happens

Post Deel time-off requests to Slack

The moment an employee or contractor asks for time off, the request is in your team's channel.

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

Send this to your assistant

Create a ClickRuntime automation: whenever someone requests time off in Deel, post their name, the dates and the leave type to #team-ops in Slack.

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 designer submits two weeks of leave in Deel on Tuesday. Her manager does not open Deel until the following Monday, and by then a client launch has been scheduled for the same dates. Time-off requests from contractors and employees sit in an approval queue that nobody is looking at, so the people who plan coverage find out late, or the requester gets silence and starts to wonder whether anyone saw it at all.

When Deel reports a new time-off request, a message goes into the Slack channel you chose. It spells out who asked, the start and end dates and the type of leave, formatted so it reads at a glance. The post appears when the request is submitted, not the next time someone remembers to check, and people can reply in the thread.

HR teams, people managers and agencies that bill by the day tend to want this most.

What you get out of it

Managers decide while dates are flexible
A request posted the minute it is submitted can be approved or discussed before project plans harden. That avoids the situation where a quick yes was easy on Tuesday but a denial on Friday, after a promise to a client, feels unfair.
Coverage planned before the gap opens
Seeing absences land in a team channel lets leads reassign tickets, move meetings and line up a backup. It also exposes clashes early, such as two people on the same small team asking for the same week, while there is still time to talk.
Requesters get an answer sooner
People who ask for leave are usually waiting to book flights. A visible post makes it likely someone replies within hours, which cuts the follow-up messages asking whether anyone has looked at it and keeps contractors feeling looked after.
Contractors and staff in one stream
Deel handles both kinds of worker, and the channel shows both. Nobody has to maintain a separate checking routine for contractors, who are easy to overlook yet matter just as much when a client has been promised their availability.
A searchable history of leave requests
Slack keeps every post, so months later you can search a name and see when time off was asked for. That is a lightweight record to point to if a request was made and later forgotten, or a dispute arises over notice periods.

How it works

What happens, step by step

When an employee or contractor asks for time off in Deel, Deel tells ClickRuntime straight away.
ClickRuntime picks out who asked, the type of leave and the dates.
A message with those details is posted to your Slack channel.

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

Post Deel time-off requests to Slackjust nowSucceeded

Slack · #team-opsLina Haddad requested Vacation: 2026-11-10 to 2026-11-14

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.

time_off_request_alerts.pyexample

from clickruntime import on_event, notify

@on_event
def handle(event):
    data = (event.json or {}).get("data", {})
    if data.get("meta", {}).get("event_type") != "time-off.created":
        return {"posted": False}
    r = data.get("resource", {})
    who = (r.get("requester") or {}).get("full_name") or r.get("recipient_name", "Someone")
    notify.slack(f"{who} requested {r.get('time_off_type', {}).get('name', 'time off')}: "
                 f"{r.get('start_date', '')[:10]} to {r.get('end_date', '')[:10]}", channel="#team-ops")
    return {"posted": True}

FAQ

Common questions

Does the Slack post include the leave type and number of days?

The message is built from the details Deel sends with the request: the person, the dates and the type of time off when it is provided. Fields Deel does not include are left out rather than guessed, so a sparse request produces a short post. Dates are shown in a plain format that is easy to read on a phone.

What happens when a request is cancelled or edited?

A webhook event is sent only for the actions you subscribe to in Deel. If you subscribe to new requests alone, a later cancellation will not produce a post, so tell your AI assistant to add the cancellation event if you want follow-up messages. Each event gets its own message in the channel.

Can I send requests for different teams to different channels?

Yes. Because the event carries the worker's details, a rule such as posting engineering requests to one channel and design requests to another is straightforward, as long as Deel includes a team or department in the data. That keeps a busy company-wide channel from filling up with requests only one team needs.

What permissions does it need?

time-off: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