Employee Feeds can publish lifecycle events that other Applaud products use to trigger automated experiences, such as onboarding, offboarding, and manager changes.
Employee record synchronization and lifecycle events are separate. You choose which events each feed publishes.
Before you begin
- Create the Employee Feed and configure field mappings.
- Confirm that the fields required for each event you want to enable are mapped. Events are generated only when the required employee fields are available.
- Identify the workflows or experiences that should respond to the events.
Available lifecycle events
| Event | Typical use |
| New joiner | Start onboarding when a new employee is synchronized and has a start date. |
| Leaver | Begin offboarding when an end date is first set on an employee. |
| Manager change | Update reporting structures and related processes. |
| Job change | Trigger experiences related to role changes. |
| Became a manager | Start manager-specific onboarding or enablement. |
| Profile update | Respond to changes such as name, email address, or other mapped attributes. |
Configure lifecycle events
- Open the Employee Feed.
- Select Edit.
- Go to the Events tab
- Enable the events your organization needs.
- Confirm that the required fields for each enabled event are mapped.
- Save the configuration.
Understand the first full synchronization
The first sync of a polling feed loads your existing employees without publishing lifecycle events, so current employees don't trigger onboarding when the feed goes live.
Events start with later syncs, when Applaud detects a change.
Spreadsheet and webhook feeds publish events from the first record they process. Make sure the events you enable are appropriate before you import a full workforce file.
Keep this behavior in mind when you:
- Bring a new feed into production.
- Expect onboarding or offboarding to start only after subsequent employee changes.
- Validate event delivery after the initial load using later synchronizations or controlled test changes.
Check event delivery
On the feed's Activity tab, Event History shows each event's status:
- Published: delivered
- Skipped: not sent, for example because the event isn't enabled or is a duplicate
- Would fire: preview only
- Failed
See Monitor Employee Feed activity.
Recommendations
- Enable only the events needed for your experiences.
- Use a separate feed for event publishing only when it requires different mappings or synchronization timing.
- Monitor event delivery after enabling events. See Monitor Employee Feed activity.
- Pause the feed when you need to stop synchronization and event processing during maintenance.