Use WPS Webhook Trigger on Windows through 2 topics: selecting the trigger condition and configuring the trigger; start from the How-to Index and follow the steps in each section.
How-to Index
| No. | Topic | Membership Requirement |
|---|---|---|
| 1 | 1. Select the Trigger Condition | Free |
| 2 | 2. Configure the Trigger | Free |
How-to Guide
1. Select the Trigger Condition
Entry: Top right of the table → Automation → Create Blank Workflow → Select trigger type → Webhook Trigger
- Open the target table and click Automation at the top right.
- Select Create Blank Workflow.
- In Step 1, under Please select a trigger condition, click Webhook Trigger.
- After you select it, check whether the Trigger Settings panel appears on the right.
Success Criteria
- Interface result: Webhook Trigger is selected and the Trigger Settings panel is visible on the right.
- Next action available: You can continue to fill in callback-related settings.
Tips While Using
- Common mistake: If you do not create a blank workflow first, you may not see the Webhook Trigger option directly.
- Environment note: This trigger can only be configured inside the Bitable automation editor.
2. Configure the Trigger
Entry: Trigger Settings panel → Callback URL / Request Parameters / Request Headers / Request Body / Authentication Method / IP Allowlist
- In the Trigger Settings panel, review the automatically generated Callback URL.
- Click the copy icon to copy the callback URL and provide it to the external system.
- In Request Parameters, enter content in JSON format.
- In Request Headers, enter content in JSON format.
- In Request Body, choose a body type and enter the related content.
- In Authentication Method, select the method you need.
- If needed, enter allowed public IP addresses in the IP Allowlist.
- Click Save and Enable to finish the setup.
Success Criteria
- Interface result: The configuration is saved and the workflow is enabled.
- Next action available: The external system can send a test request to the callback URL.
Tips While Using
- Common mistake: Incorrect formatting in request parameters, headers, or body can affect request parsing.
- Environment note: If you want to restrict access sources, enter the public IP allowlist correctly.