Skip to main content
Pipedrive automations can POST a new lead into an OpenCX workflow the moment it appears in the pipeline. The workflow can then place an outbound AI call, branch on custom fields, or enrich the lead with data from another system.
Use a Form Submit trigger in OpenCX, not a generic webhook. Form Submit triggers validate the payload against a schema you define — the workflow builder then shows typed suggestions (trigger.formData.phone, trigger.formData.name) instead of a free-form blob.

​
How it flows

​
Build the OpenCX side first

1

Create a workflow with a Form Submit trigger

In your OpenCX dashboard, start a new workflow and pick Form Submit as the trigger type.
2

Define the form schema

Add one field per value Pipedrive will send. Typical set for an outbound-call flow: name, email, phone_number, plus any custom fields (booking_code, van_model, lead_id). The field names here become the keys in formData on the Pipedrive side — keep them identical.
3

Copy the form ID

The trigger node exposes a Form ID (a ULID like 01K9SYWVMSJF5PT4AH4ACHV3F3). Copy it — Pipedrive will send it alongside the payload.
4

Finish the flow

After the trigger, add whatever nodes you need. Common chains: Make Outbound Call for phone follow-up, or Update PipeDrive Lead to enrich the lead after a downstream action lands.

​
Wire Pipedrive’s automation

1

Open Pipedrive Automations

Go to Pipedrive Automations and create a new workflow.
2

Pick your trigger

For outbound calls on new leads, use Lead created. For updates on stage changes, use Lead updated → Stage. Any Pipedrive trigger works.
3

Add an HTTP Request action

Pipedrive’s automation builder has a built-in HTTP Request step. Configure it as:
  • Method: POST
  • URL: https://api.open.cx/backend/workflow/form-submission
  • Headers: Content-Type: application/json
  • Body:
{
  "formId": "01K9SYWVMSJF5PT4AH4ACHV3F3",
  "formData": {
    "name": "{{Lead.person_name}}",
    "email": "{{Lead.person_email}}",
    "phone_number": "{{Lead.person_phone}}",
    "lead_id": "{{Lead.id}}"
  }
}
Replace formId with the ID you copied from OpenCX, and swap the merge tags for the Pipedrive fields you want to send.
4

Save and test

Create a test lead in Pipedrive. Your OpenCX workflow should fire within seconds — check the run viewer in the dashboard to confirm the payload arrived typed.

​
Outbound call payloads need E.164 phone numbers

If the next step is an outbound AI call, the phone number has to be in format before the call action runs. Pipedrive often stores phone numbers without a leading +, which the call provider rejects with customer.number must be a valid phone number in the E.164 format. Two places to fix it:
  • In Pipedrive’s HTTP Request body — concatenate a + if the number doesn’t start with one. If Pipedrive’s automation builder doesn’t support string manipulation for your layout, fix it upstream.
  • In the OpenCX workflow — add a transformation node between the trigger and the call action that prefixes + when missing.
Don’t skip this. A missing + is the single most common reason calls fire from Pipedrive but never ring through — see Troubleshooting.

​
Form Submit vs generic webhook

You can also start a workflow from a generic Webhook trigger. It works — but the payload comes through as an untyped object, and the flow builder can’t suggest fields. For anything beyond a proof of concept, use Form Submit.
Form SubmitGeneric Webhook
Payload shapeEnforced against your schemaFree-form JSON
Builder suggestionsTyped (trigger.formData.phone)Untyped
URLapi.open.cx/backend/workflow/form-submissionUnique per trigger
Body wrapper{ formId, formData }Whatever you send

Update Lead Action

Pair a Pipedrive-triggered workflow with a write-back to the same lead.

Connect

Credentials for the write-back side.

Overview

Capabilities and patterns at a glance.

Troubleshooting

Payload untyped, phone-format errors, workflow not firing.