Formidable Forms Setup
Step 1: Enable the Integration
- Open the Settings page in Pipedrive Utilities.
- Navigate to the Formidable Forms pane.
- Toggle Enable Formidable Integration on.
Step 2: Configure Connection Settings
Fill in the following fields in the Formidable Forms settings pane:
| Field | Description |
|---|---|
| WordPress Site URL | The root URL of your WordPress site (e.g., https://example.com). The server appends /wp-json/frm/v2/... to this URL when calling the Formidable REST API. |
| Formidable API Key | Your Formidable REST API key. Found in WordPress under Formidable > Global Settings > API. The server uses HTTP Basic authentication with this key as the username. |
| Webhook Bearer Token | Click Generate to create a random bearer token. This token secures the webhook endpoint. Copy it; you will paste it into WordPress. |
Step 3: Copy the Webhook URL
After saving, the settings page displays your webhook endpoint URL:
https://<your-worker-domain>/webhook/formidable/<companyId>
The companyId is your Pipedrive company ID, shown automatically on the settings page.
Step 4: Configure WordPress
In your WordPress admin, edit the Formidable form you want to connect:
- Go to Settings > Actions & Notifications for the form.
- Add a Webhook action (or edit an existing one).
- Configure the webhook:
| Setting | Value |
|---|---|
| Webhook URL | The endpoint URL copied from Step 3 |
| Format | JSON |
| Method | POST |
- Add a custom request header for authorization:
| Header Name | Header Value |
|---|---|
Authorization |
Bearer <your-token> |
Replace <your-token> with the bearer token generated in Step 2.
The webhook payload only needs to include form_id and entry_id. Formidable’s default webhook action sends these automatically. The server fetches the full entry data via the REST API, so you do not need to map individual fields in the webhook action itself.
Step 5: Configure an Automation User
The webhook handler requires an automation user to be configured in the General settings pane. This is the Pipedrive user whose OAuth token is used for all webhook-triggered API calls. See the General settings documentation for details.
If the automation user’s token expires and cannot be refreshed, all incoming webhooks will return a 503 error. Ensure the automation user has logged in to Pipedrive Utilities at least once so their token is stored, and enable email notifications for the “Automation user token cannot be refreshed” category to be alerted if this happens.
Step 6: Set Up Field Mappings
Once the connection is established, configure per-form field mappings to control how form submissions are translated into Pipedrive records. See Field Mapping for details.