Hourly

Tell Slack when someone joins in Rippling

Each new hire shows up in Slack with their role and start date, so the people setting things up can start.

Runs: Hourly
Apps: Rippling
AI: Not needed
Access: read workers scope

Send this to your assistant

Create a ClickRuntime automation: every hour, check Rippling for newly added employees and post their name, job title, department and start date to #new-hires 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

When someone joins a company, the people who need to know are rarely in HR. IT must set up accounts, finance wants to add a card, the team lead should plan onboarding, and colleagues would like to say hello. Without a prompt, each learns through gossip or after the person asks where to sit, and onboarding steps are missed.

Every hour, ClickRuntime lists workers from Rippling and compares them with the IDs it has stored. When a new person appears, it sends a notification with their name, role and start date. Each person is announced once, because their ID is saved after the first alert and later checks skip it.

It is most useful in companies where IT, finance and team leads prepare for new hires and rely on HR data to get started, and who would otherwise hear about new people secondhand.

What you get out of it

Setup starts as soon as HR records the hire
IT can create accounts and order equipment on the day the record appears. Waiting for an email thread cuts lead time and prevents a new starter sitting without a laptop.
Teams hear it officially
People learn about a new colleague from a clear message, not from rumor. That helps the team plan work and prepare a welcome. Rumors cause confusion, a clear message does not.
Role and date are included
Knowing the job title and start date tells each recipient what they need to do. A new engineer needs different preparation from a new salesperson. Recipients know straight away what applies to them.
Each hire is announced once
Saving worker IDs prevents repeats. You get one clear message per person, even though the check runs every hour. Nobody sees the same name twice. The hourly check never turns into hourly noise.
Fewer missed onboarding steps
Finance, IT and facilities all hear at the same time. Tasks that used to depend on someone remembering to forward an email now start by themselves. New starters notice the difference on day one.

How it works

What happens, step by step

Every hour, ClickRuntime lists the workers in Rippling.
It compares them with the people it has already seen, to find anyone new.
Each new hire is posted to your Slack channel with their role, team and start date, so the people setting things up can get going.

Before it runs live

Connect Rippling

What you get

RunsHourly

Tell Slack when someone joins in Ripplingtoday, 9:00Succeeded

Slack · #new-hiresNew hire: Jordan Blake, Account Executive in Sales, starting 2026-11-03

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

new_hire_notification.pyexample

from clickruntime import on_trigger, credentials, http, state, notify, report_fetched

def employees():
    resp = http.get("https://api.rippling.com/platform/api/employees",
                    headers={"Authorization": f"Bearer {credentials.secret('RIPPLING_API_TOKEN')}"},
                    params={"limit": 100})
    resp.raise_for_status()
    return resp.json()

@on_trigger
def run(event):
    staff = employees()
    known = state.get("known")
    new = [e for e in staff if known is not None and e["id"] not in known]
    report_fetched(len(new))
    if known is not None and not new:
        return {"summary": "Nothing new"}
    for e in new:
        notify.slack(f"New hire: {e['name']}, {e.get('title')} in {e.get('department') or 'no department'}"
                     f", starting {e.get('startDate')}", channel="#new-hires")
    state.set("known", [e["id"] for e in staff])
    return {"new": len(new)}

FAQ

Common questions

How does it know a worker is new?

It keeps a list of worker IDs it has already seen. Each hour it compares the current list from Rippling with the stored one, and any ID that is not in the stored list is treated as new, then added to it.

Will it announce people already employed when I first set it up?

No. The first run records everyone currently in Rippling without notifying, and only people added afterwards trigger messages. That avoids a flood of announcements about existing staff on the first day. Existing staff are never re-announced.

Does it include contractors?

It reflects the workers Rippling returns to the connected account, which depends on which worker types are in your Rippling workspace and what your API access allows. Employees are included, and contractors appear if Rippling returns them. Check which worker types your Rippling workspace holds.

What permissions does it need?

read workers scope. 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 each time it checks. Checks that find nothing new and stop right away aren't counted.

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.

On a schedule