Connect Feathery and Personio

Both apps 40Feathery 13Personio 27

• Trigger
  Data Received

  Triggers when an end user submits or updates data on a Feathery form.

• Trigger
  Form Completion

  Triggers when an end user completes a Feathery form.

• Action
  Create Hidden Field

  Creates a hidden field in your Feathery account.

• Action
  Create or Fetch User

  Creates a Feathery end user with the given ID, or returns the existing user, including its SDK key.

• Action
  Create or Update Submission

  Sets field values for a Feathery user and initializes submissions on the given forms.

• Action
  Delete User

  Deletes a Feathery end user and their submissions.

• Action
  Get User Field Data

  Returns every field value a Feathery user submitted across forms.

• Action
  Get User Form Session

  Returns a Feathery user's form session: every form they are working on and their progress.

• Action
  List Document Templates

  Returns document templates uploaded by your Feathery team, optionally filtered by name or tags.

• Action
  List Forms

  Returns your Feathery forms, optionally filtered by tags or active status.

• Action
  List Form Submissions

  Returns submissions for a Feathery form, optionally filtered by user, completion and update time.

• Action
  List Hidden Fields

  Returns all hidden fields in your Feathery account.

• Action
  List Users

  Returns your Feathery end users, optionally filtered by creation time or a field value.

• Trigger
  Employee Updated

  Triggers when an employee is updated.

• Trigger
  Employment Updated

  Triggers when one or more Employment details of a Person are updated

• Trigger
  New Absence

  Triggers when a new absence is created.

• Trigger
  New Candidate

  Fires when a new recruiting candidate is added in Personio.

• Trigger
  New Employee

  Triggers when a new employee is created.

• Trigger
  New Employment Created

  Triggers when one or more Employment details of a Person are created

• Trigger
  New Open Position

  Triggers when a new open position is created.

• Action
  Add project

  /v2/projects - create a project.

• Action
  Create Absence

  Creates a new absence.

• Action
  Create Attendance

  Creates a new attendance.

• Action
  Create Employee

  Creates a new employee.

• Action
  Delete absence

  /v2/absence-periods/{id} - delete an absence period.

• Action
  Delete attendance

  /v2/attendance-periods/{id} - delete an attendance period.

• Action
  Delete person

  /v2/persons/{id} - delete a person.

• Action
  Find Absence

  Finds an absence by employee ID.

• Action
  Find Employee

  Finds a employee based on email.

• Action
  Find Person

  Finds a person by their Personio ID, name, last name and email, optionally including their absence information.

• Action
  Get Employment

  Retrieves one employment of a person by id: position, status, type, working hours, org units, cost centers, supervisor, office, legal entity, dates.

• Action
  List absence types

  /v2/absence-types - list absence types.

• Action
  List Compensations

  Lists compensations filtered by person.id and a start_date/end_date window; returns id, amount, interval, type, effective_from per record.

• Action
  List legal entities

  /v2/legal-entities - list legal entities.

• Action
  List org units

  /v2/org-units - list org units.

• Action
  List projects

  /v2/projects - list projects.

• Action
  Update absence

  /v2/absence-periods/{id} - update an absence period.

• Action
  Update Attendance

  Updates an existing attendance.

• Action
  Update Employee

  Updates an existing employee.

• Action
  Update Employment

  updates an employment (position, department, office, weekly hours, status, etc.); requires personio:persons:write. Fires the employment.updated webhook.

No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.