For AI agents: an index of this documentation is at https://developer.rippling.com/llms.txt. Public pages have a Markdown version at the same URL with .md added.

Skip to main content
guide

Automation triggers

Choose the one event, schedule, or inbound webhook that starts an automation.

Use with AI:Rippling AI ChatGPT Claude Cursor

Overview​

The first step in creating an automation is to define the trigger. The trigger is the catalyst that initiates the automation. Every automation has one and only one trigger.


Trigger types​

The following types of triggers are available:

  • Relative to someone’s start date (basic)
  • Relative to a date
  • On a set schedule
  • When something happens
  • Object creation and updates
  • Trigger manually
  • From a webhook

When you open the trigger selector, you'll also see a Popular Triggers category with a collection of the triggers customers use most.

Relative to someone’s start date (basic)​

This basic trigger option lets you create unlimited free automations to help you automate new hire onboarding. Use this option if you want the automation to trigger based on someone’s first day of work.

When you use this trigger, your automation is limited to sending email and assigning tasks, whereas the other trigger options let you access the full suite of automation steps.

Relative to a date​

Use this option if you want your automation to trigger based on a date that’s stored in Rippling. For example:

  • Employee’s first day
  • Employee’s last day
  • Birthday
  • Work anniversary
  • Device purchase date
  • Company pay run approval date

On a set schedule​

Use this option if you want your automation to run on a regular schedule that you define. For example:

  • Every Monday at 9 PM
  • Every last day of the month at 7 AM
  • Every quarter on the first day the month

If you want to take certain steps on a regular cadence, you could create automations such as:

  • Every Saturday at 5 PM EST, send a report with last week’s performance to your CFO.
  • Every quarter, survey your employee satisfaction and set up follow up meetings if needed.

You can optionally add filter conditions so the automation only runs for a selected set of records. For example, every Monday, send an email that includes a list of contractors whose contracts are expiring in the next 30 days.

Frequency options​

After selecting the On a set schedule trigger, customize the schedule further by choosing from Rippling's available frequency options.

OptionDetails
DailyEvery day, at a time you choose.
HourlyEvery hour.
OnceOne time, on a specific date and time.
WeekdaysMonday through Friday, at a time you choose.
WeeklyOn the days of the week you select, every week.
BiweeklyOn the days of the week you select, every two weeks.
MonthlyOn a specific day of the month, such as the 1st or the 15th.
Monthly on the same day of the weekOn a specific weekday in a specific week of the month, such as the second Tuesday.
QuarterlyEvery 3 months, on a month and day you choose.
AnnuallyOnce a year, on a specific month and day.
Cron expressionA five-field expression (minute hour day-of-month month day-of-week) and a timezone. For example, 0 12 * * * runs every day at 12:00. It can take up to 15 minutes after the scheduled time for the automation to trigger.
CustomAn interval you define, such as every 15 minutes, every 6 hours, or every 2 months.

Use a cron expression when you need to use multiple schedule specifications at one time. For example, trigger an automation:

  • More than once on the same day: 0 9,17 * * 1-5 runs at 9:00 and 17:00, Monday through Friday.
  • On several dates in the same month: 0 8 1,15 * * runs at 8:00 on the 1st and the 15th of each month.
  • Only in certain months: 0 9 1 1,4,7,10 * runs at 9:00 on the first day of January, April, July, and October.

Variables in scheduled automations​

When you use filter conditions, you’ll have access to variables from the records that match the conditions. For example, if you’ve filtered the automation to only run for contractors, you could send an email that includes a variable for the contractor’s first name. You could also add any other variables from the Employee object, like the contractor’s location, pay rate, or contract type.

However, if you set up a scheduled automation that doesn’t have any filter conditions, you will not have access to any variables in downstream steps. This is because the automation simply runs on a schedule, and there is no underlying data that can be used to populate variables.

How scheduled automations with filter conditions run​

When you add filter conditions to a scheduled automation:

  1. The automation triggers on your defined schedule (e.g., Monday at 9:00 AM PST).
  2. Rippling compares all records to the filter conditions.
  3. The automation runs once for each record matching the conditions, up to 5,000 records. The automation is executed in parallel for all matching records. If there are more than 5,000 matching records, or if no records match the condition, the automation will not run.

Rippling recommends running a test with a small number of records to see the outcome of your automation before enabling it for a large number of records. For example, you could add a filter condition to run the automation only for super admins or for one specific individual.

Scheduled automations are evaluated by a background job that runs every 15 minutes. For more information, see Troubleshooting.

When something happens​

Use this option if you want to select from a set of predefined events to trigger your automation. For example:

  • Hiring request is submitted
  • Employee returns from leave
  • Document is sent
  • Course is completed

There are several predefined events from which you can choose.

Object creation and updates​

You can also trigger automations any time a record that meets the conditions you specify gets created, updated, or deleted. For example, trigger an automation when:

  • A company pay run's check date changes (Rippling Payroll triggers apply to both US and Global Payroll)
  • Someone's compensation changes
  • A new license is added to the Licenses custom object
  • A GitHub pull request is created

If your trigger uses a condition like Employee is updated (including individual employees and bulk updates to many employees) or Profile change is effective and no narrowing filters have been applied, the automation will run for any update, including system updates or formula field recalculations.

Use Changes or Changes to when you only want the automation to run when that field changes. For more information, see Filter conditions and Troubleshooting.

Trigger manually​

Use this option if you only want your automation to run when you trigger it manually. The automation will not automatically trigger on its own.

From a webhook​

An incoming webhook lets a system outside of Rippling start an automation by sending a POST request to a unique webhook URL. For more information, see Trigger an automation using a webhook.

Slack​

Watch a Slack channel and trigger an automation when someone posts a message or adds a reaction.

This feature is only available to companies with an active Rippling AI trial or subscription.


Use filter conditions to qualify a trigger​

You can add filter conditions to most automations to further qualify when the automation should run. For example, trigger the automation only for people in the Support department.

Note that you cannot add filter conditions when triggering an automation manually.

For more information, see Filter conditions.


Permissions to trigger automations​

Automations only trigger based on the apps and data you have permission to access. For example, if you have access to basic data, you’ll be able to trigger automations based on changes to things such as work location and start date, but you won’t be able to trigger automations based on changes to non-sensitive data such as home address or sensitive data such as compensation. Keep this in mind as you select your trigger event.

For more information, see Automation permissions.


See also​