Log support requests as Pipedrive activities
A customer help submission creates a Pipedrive activity on that customer's record, assigned to the account owner.
New submission on your "Customer help" form
Create an Activity on the matching deal or person and assign it to the account owner
One-directional. A submission triggers the action — nothing is written back into your form.
Support requests that arrive by form tend to land in a mailbox that nobody owns. Turning each one into a Pipedrive activity gives it a due date and a named owner, which is the difference between a task and a hope. The customer's existing record is where it belongs.
Account managers at services businesses and B2B vendors get the most from it. Reported issues sit next to the renewal they could sink, so the person who owns the relationship sees the problem without checking a second system.
Setting it up
- 1
Publish your customer help form in formformform from the Customer Complaint Form template, and link to it from your help pages and your order confirmation emails.
- 2
Make Email Address required — it is the only value this automation can use to find the right Pipedrive record.
- 3
In Zapier, use formformform's New Submission trigger on this form, then add Pipedrive's Find Person action searching on Email Address.
- 4
Set that step to continue only on a match, and add a fallback path that creates the person from Customer Name when the sender is not yet in Pipedrive.
- 5
Add Pipedrive's Create Activity action, set the type to Call or Task, and build the subject from Complaint Type and Order or Account Number.
- 6
Put Complaint Details and Desired Resolution into the activity note, so the owner reads the whole report without opening another tab.
- 7
Set the due date to today or tomorrow, and assign the activity to the found person's owner rather than a fixed user, so it reaches the account owner.
- 8
Submit a test request from a known customer's address, confirm the activity appears on their record with the right owner, then enable the Zap.
What maps where
Using the Customer Complaint Form as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Pipedrive |
|---|---|
| Email Address | Search key for Find Person — decides which record the activity attaches to |
| Customer Name | Person name on the fallback branch when no match is found |
| Complaint Type | Activity subject line and activity type |
| Order or Account Number | Activity subject, so the owner has the reference before opening it |
| Complaint Details | Activity note body |
| Desired Resolution | Activity note body, below the report itself |
Variations worth knowing
If the customer has a live deal, add a Pipedrive Find Deal step on their person ID and attach the activity there instead. Support friction during a renewal cycle then shows up on the card the rep is already watching every week.
Branch on Complaint Type in Zapier: billing goes to finance with a same-day due date, everything else to the account owner with two days. One activity type for everything means the urgent items look identical to the routine ones in a task list.
If something isn't arriving
The due date field was left blank, so Pipedrive files the activity undated and it never appears in anyone's Today view. Set it explicitly — today's date from a Zapier Formatter step is enough — and add a due time if your team works from the calendar.
Two people at the same organisation matched because the Find Person step searched on name rather than address. Search on Email Address only. Names repeat across a company and across your whole database; email addresses do not.
Frequently asked questions
How do I assign a form-generated task to the right account owner?
Find the person first, then use their owner ID as the activity's assigned user rather than picking a fixed name. The task then follows account ownership changes automatically, without anybody editing the Zap each time a territory shifts.
What if the customer who submits is not in Pipedrive yet?
Add a branch that creates the person from Customer Name and Email Address, then creates the activity against that new record. Silently skipping unmatched submissions is worse: the report still exists in formformform, but nobody working in the CRM ever sees it.
Is a Pipedrive activity a substitute for a helpdesk?
Not really. An activity gives you a due date, an owner and a place on the customer's timeline, which is enough at low volume. Once you need queues, response targets and threaded replies, a dedicated support tool alongside Pipedrive makes more sense.
Related automations
- Add webinar registrants as labelled people
Every webinar registrant becomes a Pipedrive person carrying a registration label you can filter on later.
- Attach customer feedback to the Pipedrive contact
Feedback lands as a note on the customer's Pipedrive record, next to their open deals.
- Open a deal when someone books a demo
A demo request opens a deal at the Demo scheduled stage, with the person attached and pipeline value updated immediately.
- Open a deal with a note for every quote request
A quote request opens a Pipedrive deal and files the full set of answers as a note on the same card.
- Send website enquiries to the Pipedrive Leads Inbox
Each contact sales submission becomes a Pipedrive lead in the Leads Inbox, with the person and organisation already linked.
- Add newsletter signups to Zoho CRM as tagged contacts
Every newsletter opt-in becomes a Zoho CRM contact carrying a tag you can build a campaign list from.
Build the form first
The automation needs somewhere to fire from. Publish a form, connect it once, and every submission from then on runs this flow.
Start free