---
title: "Create a webhook"
description: "Let another system submit a form on an employee's behalf: add a webhook to the form, choose which HRIS id identifies the employee, mint the secret once, and read the log of what arrived."
sidebar:
  order: 2
area: flows
feature: forms
appPath: /flows/home
lastVerified: 2026-10-22
version: "2026-10-16"
audience: admin
screenshots:
  - id: flows-forms-webhook-drawer
    caption: The Settings drawer on a form, with the webhook's URL, header, subject and example body.
related:
  - flows/forms/reference-webhook-api
  - flows/forms/build-a-form
  - notices
intercom:
  - id: "16858360"
    title: Create a Webhook (Pyn 2)
    url: https://intercom.help/pyn/en/articles/16858360-create-a-webhook-pyn-2
    note: replaces
---

Some answers already exist in another system: a completed training in your LMS, an equipment request in a ticketing tool, a signed document. A webhook on a form lets that system post the answer into Pyn as a submission, recorded against the employee it names.

## Before you start

- You are an Admin.
- The form is built and published, with field labels your other system can map to. See [Build a form](https://support.pynhq.com/flows/forms/build-a-form/).
- The other system can send each employee's id from your HRIS, the same id Pyn has from that integration.

![A form's webhook: the endpoint, the header to send, the subject source system and the example body.](https://support.pynhq.com/media/flows/forms/flows-forms-webhook-drawer.png)

## Steps

1. In Pyn, open **Flows** in the left navigation, select **Forms**, then the form.

2. Select **Settings** on the rail at the right of the editor. The drawer reads **Add a webhook to let another system submit this form on an employee's behalf.** Select **Add Webhook**.

3. Under **Subject**, select the source system whose id the other system will send, for example **BambooHR Employee ID** or **Workday Worker ID**. The description reads **The submission is recorded against the employee holding this id.**

4. Copy the **URL** and note the header: `Authorization: Bearer <secret>`.

5. Select **Create Secret**. The drawer reads **Copy this secret now. It is shown once and cannot be retrieved later.** Copy it into the other system, then select **Done**.

6. Read the example under **Post a body of this shape.** It names each field by its alias (the label in camel case) with a sample value, plus `subject_id`.

7. Send a test payload from the other system and read the log at the foot of the drawer (**Payloads this webhook has taken, and what became of them.**). A green entry reads **Recorded a submission for the ... identifier ...**; a red one names the problem.

> **Caution:** A lost secret cannot be recovered. Select **Replace Secret** to mint a new one; the drawer warns **The current secret stops working immediately. Anything calling this webhook will need the new one.**

## Rotating the secret and reading the log

- **Replace Secret** rotates the secret in one step and the old one stops working at once; update the calling system before you confirm.
- The log shows the most recent entries; the export icon beside it downloads the whole log as CSV (`receivedAt`, `outcome`, `action`, `code`, `message`, `eventId`, `subjectId`, `submissionId`).
- A dropped payload also raises a notice in [Notices](https://support.pynhq.com/notices/) keyed by its code, so the same mistake repeated keeps one notice current rather than many. The workspace's notification settings decide whether every admin is emailed or the owner alone.
- Archiving the webhook from its panel menu stops it accepting anything.

## What you should see

Accepted payloads appear as submissions in the form's **Activity** drawer, and the employee's record carries any Buddy or Mentor value. Each employee can be submitted once per webhook; a repeat is logged as `already-submitted`. [Webhook API](https://support.pynhq.com/flows/forms/reference-webhook-api/) lists the endpoint, headers, body, responses and every log code.

## Related

- [Webhook API](https://support.pynhq.com/flows/forms/reference-webhook-api/) for the exact request and responses.
- [Build a form](https://support.pynhq.com/flows/forms/build-a-form/) for the fields a payload fills.
- [Notices](https://support.pynhq.com/notices/) for where failures surface.

## Related Intercom articles

- [Create a Webhook (Pyn 2)](https://intercom.help/pyn/en/articles/16858360-create-a-webhook-pyn-2) — replaces