The moment it happens
Note outside events on Pipedrive contacts
When something happens elsewhere, like a support ticket, it is added as a note on the matching person.
- Runs
- The moment it happens
- Apps
- Pipedrive
- AI
- Not needed
- Access
- read+write
Send this to your assistant
Create a ClickRuntime automation: give me a link my help desk can send events to. Find the Pipedrive person by the email in each event and add a note with the ticket subject and status.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
A customer who is also in Pipedrive may have opened a support ticket, merged a pull request, attended a webinar or started a trial. The sales rep sees none of it. They call to ask how things are going without knowing that the person reported a serious bug yesterday, which makes the call awkward and wastes a chance to help or to upsell at the right moment.
When another tool sends an event to the webhook, the person is found in Pipedrive by email, and a note describing the event is added and linked to that person. The note appears in their timeline alongside calls and emails, so everything the rep needs is in the usual place. A common variation is to log only certain event types.
It is useful for teams who want their CRM to reflect product usage, support history and other signals without manual entry.
What you get out of it
Calls start with full context
A rep who knows about yesterday's ticket opens with empathy and a solution. That turns a routine check-in into a moment that builds trust. Preparation like this is what separates a thoughtful rep from one reading from a script. Customers notice the difference.
The CRM becomes the source of truth
When events from several tools land in one timeline, people stop switching between systems. A single view of the customer saves time and avoids missed context. Support, engineering and sales all see the same history, and arguments about who knew what disappear.
No manual data entry
Copying events into Pipedrive by hand is tedious and rarely done. Automatic notes mean the history is complete, including events that happen at night or on weekends. Anything that happens at night or at the weekend is captured too, with no one needing to remember.
Spot buying signals
A note that a contact visited the pricing page or started a trial tells a rep when to reach out. Timing a message to real activity beats cold follow-ups. A message that arrives right after real activity feels relevant instead of random.
A record for account reviews
When a customer's account is reviewed, the notes show what happened and when. That helps with renewals, escalations and deciding how to treat the relationship. Context like this also supports fair decisions on discounts and priority support.
How it works
What happens, step by step
When another tool sends an event, such as a support ticket being solved, ClickRuntime receives it straight away.
It searches Pipedrive for the person with the matching email address.
A note describing the event is added to that person, like "Support ticket #8812: Invoice shows wrong VAT number (solved)".
Before it runs live
- Connect Pipedrive
- Paste your automation's link into the other app's webhook settings
What you get
Build your own
Need it to work differently?
Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.
Changes you can ask for
- Act only on the items that match your own rules, and skip the rest
- Add an AI step, for example to summarize, sort or draft a reply
- Add another app, for example also send it to Slack
- Combine it with other Pipedrive steps into one automation
Under the hood
The code that runs this automation
from clickruntime import on_event, credentials, http, log
API = "https://api.pipedrive.com"
@on_event
def handle(event):
ticket = event.json or {}
headers = {"Authorization": f"Bearer {credentials.connection('pipedrive', 'work')}"}
found = http.get(f"{API}/api/v2/persons/search", headers=headers,
params={"term": ticket.get("email", ""), "fields": "email", "exact_match": "true"}).json()["data"]["items"]
if not found:
log.info("no matching person", {"ticket": ticket.get("id")})
return {"noted": False}
person_id = found[0]["item"]["id"]
http.post(f"{API}/v1/notes", headers=headers, json={
"person_id": person_id,
"content": f"Support ticket #{ticket.get('id')}: {ticket.get('subject')} ({ticket.get('status')})"}).raise_for_status()
return {"noted": True, "person": person_id}FAQ
Common questions
What if no person matches the email?
Which tools can send events?
Is the note linked to the deal or the person?
What permissions does it need?
Does it need AI?
How many runs does it use?
Can I change how it works?
Related
You might also like
Turn form submissions into Pipedrive leads
Each form submission creates or updates the person and adds a lead with their answers, and you hear about it in Slack.
See how it worksPost won Pipedrive deals to Slack
Every won deal is posted to your wins channel with its name, value and owner.
See how it worksPost new Pipedrive deals to Slack
Your team sees each new deal's value and stage in Slack within minutes.
See how it worksKeep exploring
Set up “Note outside events on Pipedrive contacts” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.
