Special workflows for Pipedrive.
Each scenario shows the trigger, the Volimox handoff, and the human checkpoint. These are concrete workflow blueprints, not a claim that every connection is live today.
Qualified request to deal
Create a visible Pipedrive deal when a request is ready for sales follow-up.
Starts when
A Volimox conversation contains the required contact, service, and timing fields.
Result
Every qualified request has a pipeline stage and accountable next activity.
Volimox workflow
- 01Volimox finds or creates the Pipedrive person and organization.
- 02Volimox creates a deal in the configured pipeline and stage.
- 03The owner receives a next activity with the original conversation context.
Human checkpoint
Deal creation waits for qualification and duplicate checks.
Deal stage to next activity
Keep the next sales or dispatch action moving when a deal advances.
Starts when
A Pipedrive deal stage changes on a linked Volimox opportunity.
Result
Pipeline movement produces a concrete next step instead of a stale record.
Volimox workflow
- 01Volimox reads the new stage and the last conversation state.
- 02Volimox creates the next activity or updates the existing one.
- 03The owner completes, reassigns, or closes the activity with a reason.
Human checkpoint
Stage changes do not create duplicate activities for the same transition.
Supported triggers and actions.
A trigger starts the workflow. An action is the controlled operation Volimox performs after the rules pass.
Triggers
- New person
- New organization
- New deal
- Deal stage changed
Actions
- Create person
- Create deal
- Update deal
- Create activity
Detailed connection code.
This server-side TypeScript reference follows the same connection → action → mapped input pattern used by modern automation platforms. Provider credentials remain inside the approved connection; browser code never receives them.
TypeScript · server only
Create a Pipedrive deal
import { createZapierSdk } from "@zapier/zapier-sdk"
const zapier = createZapierSdk({
apiKey: process.env.ZAPIER_API_KEY,
})
export async function runPipedriveAction() {
const { data: connection } = await zapier.findFirstConnection({
app: "pipedrive",
owner: "me",
})
if (!connection) {
throw new Error("No approved Pipedrive connection was found")
}
const result = await zapier.runAction({
app: "pipedrive",
action: "create_deal",
connection: connection.id,
input:
{
"title": "{{lead.name}} — {{lead.service}}",
"personId": "{{lead.pipedrivePersonId}}",
"pipelineId": "{{env.PIPEDRIVE_PIPELINE_ID}}",
"stageId": "{{env.PIPEDRIVE_STAGE_ID}}",
"value": "{{lead.estimatedValue}}",
"currency": "USD"
},
})
return result.data
}Connection setup.
The setup path is specific to the provider. We will never ask you to paste credentials into a public page.
Pipedrive OAuth
A reviewable connection, step by step.
- 01Choose a Pipedrive account
- 02Select pipeline and stages
- 03Review person and deal scopes
This app is cataloged and its workflow contract is defined. We will enable the connection after provider access and sandbox verification.
Related apps