FeedbackPulse for Zapier
Use the FeedbackPulse Zapier connector to create or update employee records when something happens in another app, such as a new hire in an HR system.
Connect a workspace
Section titled “Connect a workspace”- A workspace Admin opens Settings > Integrations > API Clients in FeedbackPulse, creates an API client, and selects
employees:read,employees:write, andemployees:sync. - In Zapier, add a FeedbackPulse action to a Zap and connect an account.
- In API key, paste the key without the
Bearerprefix. MCP tokens do not work. - In Workspace label, enter a name to recognize this connection, such as Example Workspace.
Zapier uses the read scope to test the connection, to fill the Manager dropdown, and to read the saved employee after Create or Update Employee.
Choose an employee action
Section titled “Choose an employee action”| Action | Use it for |
|---|---|
| Create or Update Employee | Create or update an employee profile from an HR system, matched by HR system source and HR system employee reference. This action preserves existing account status and does not send invitations. |
| Create Employee | Create an employee, or restore a deleted employee with the same email. Optionally assign a manager and send an account invitation. |
When your trigger supplies a stable event ID, map it to Event key so retries of that event use the same idempotency key.
Create or Update Employee fields
Section titled “Create or Update Employee fields”| Field | Required | Help text |
|---|---|---|
| HR system source | Yes | Stable source/account namespace, for example bamboohr-example. Keep this unchanged across Zaps for the same HR account. |
| HR system employee reference | Yes | The employee’s unique identifier in your HR system. Map it from your HR system’s trigger. FeedbackPulse uses it with HR system source to find the same employee on later runs. Do not map an event ID here. |
| Yes | ||
| Name | No | |
| Employment type | No | Leave blank to preserve an existing value. New employees default to Full time. |
| Job title | No | |
| Department | No | |
| Employee number | No | |
| Hire date | No | Use YYYY-MM-DD. |
| Event key | No | Map the ID of the event that triggered this Zap, with a prefix unique to this step, so FeedbackPulse can recognise a repeat of the same event. Leave blank for no duplicate protection. |
Employment type offers Full time, Part time, and Contractor.
The step returns the employee: Employee ID, Name, Email, Job Title, Department, Employee Number, Hire Date, Employment Type, Employment Status, Account Status, Access Status, Is Manager, Termination Date, Created At, Updated At, Manager ID, and Manager Name. It also returns Sync Result, Employee Link, Warnings, and Has Warnings. Sync Result is created or updated. If FeedbackPulse does not save the employee, the step fails with the reason. For example, a change that would terminate the last active admin of the workspace fails with the code last_active_admin.
After the save, the step reads the employee back to fill these fields. If FeedbackPulse limits the request rate or is briefly unavailable during that read, the step fails and Zapier runs it again. Repeating the update is safe. If the read fails for another reason, the step still succeeds and the employee is saved: Employee ID, Email, Sync Result, and Employee Link are filled, the other employee fields are empty on that run, Warnings contains employee_read_failed, and Has Warnings is true.
Create Employee fields
Section titled “Create Employee fields”| Field | Required | Help text |
|---|---|---|
| Name | Yes | |
| Yes | ||
| Employment type | Yes | |
| Job title | No | |
| Department | No | |
| Employee number | No | |
| Hire date | No | Use YYYY-MM-DD. |
| Manager | No | Select an employee in this workspace or map their public Employee ID. |
| Send account invitation | No | Sends an account setup email. Does not invite to or launch a survey. Check output warnings for delivery failures. |
| Event key | No | Map the ID of the event that triggered this Zap, with a prefix unique to this step, so FeedbackPulse can recognise a repeat of the same event. Leave blank for no duplicate protection. |
Employment type offers Full time, Part time, and Contractor, and starts at Full time.
The step returns the employee: Employee ID, Name, Email, Job Title, Department, Employee Number, Hire Date, Employment Type, Employment Status, Account Status, Access Status, Is Manager, Termination Date, Created At, Updated At, Manager ID, and Manager Name. It also returns Employee Link, Warnings, and Has Warnings.
API operations behind the connector
Section titled “API operations behind the connector”Each Zapier step calls one REST API operation. The reference pages list the fields, responses, and errors for each one.
| Zapier step | API operation | Scope |
|---|---|---|
| Connection test and Manager dropdown | List employees (GET /v1/employees) |
employees:read |
| Create or Update Employee, read of the saved employee | Get an employee (GET /v1/employees/{employee}) |
employees:read |
| Create Employee | Create an employee (POST /v1/employees) |
employees:write |
| Create or Update Employee | Sync employees (POST /v1/employees/sync) |
employees:sync |
If you have questions about the connector, contact support.