The most requested automation in any CRM is also the simplest to say out loud: when something changes, do something about it. Until now, the Pipeline CRM Zapier integration couldn’t do it. Zaps could fire when a deal, person, or company was created, but not when one changed. That gap ruled out a whole category of everyday automations, and it’s the first thing this rebuild fixes.

We rebuilt the integration end to end. Here’s what’s new, why it matters, and three workflows you can set up this week.

What changed in the Pipeline CRM Zapier integration?

The Pipeline CRM Zapier integration went from a small set of create-only triggers to full coverage of the record lifecycle: created, updated, won, lost, converted, and deleted. The numbers tell the story quickly.

Owner fields are now clearly labeled “Owner,” branding is consistently “Pipeline CRM,” and a number of smaller reliability issues from the previous version are resolved along the way.

Zaps can finally react to change

The headline additions are the Updated Deal, Updated Person, and Updated Company triggers: a Zap can now run whenever a record changes, not only when it’s created. If a deal’s value gets revised, a person’s phone number changes, or a company moves territories, your other tools can know about it immediately.

Two more additions sharpen that further:

• Deal Won and Deal Lost. Dedicated triggers for closed outcomes. Fire the handoff, start onboarding, post the win alert, or log the loss reason the moment a deal closes, not at the end-of-week export.
• Field-level triggers. Deal Field Changed, Person Field Changed, and Company Field Changed watch one field you pick and fire only when that field changes. That turns broad, noisy automations into precise ones: reassign a follow-up task only when the deal owner changes, not on every edit.

There’s also a New Customer trigger and a matching Convert Company to Customer action, so the prospect-to-customer transition can both start a Zap and be performed by one. And for teams that mirror CRM data into a warehouse, billing tool, or backup, new Deleted Deal, Deleted Person, and Deleted Company triggers let the mirror flag or remove records when they’re deleted in Pipeline CRM. That last one is a genuine differentiator: it’s the piece two-way sync setups usually have to live without.

Calendar sync now works both directions

Before, Zaps could create calendar tasks and events in Pipeline CRM but never update them. New Update Calendar Event and Update Calendar Task actions close the loop: when a meeting moves in your external calendar, the Pipeline CRM entry can move with it, including time, status, and details. Add the new Upload Document action, which attaches a file from a URL onto a person, company, or deal, and things like signed contracts and generated PDFs can file themselves onto the right record.

Custom fields work everywhere now

Custom fields used to be the sore spot: mostly invisible to Zapier. Now they appear automatically as inputs you can set in create and update actions, outputs you can map into later Zap steps, and conditions you can search on. Multi-select custom fields are supported, and you can clear a value back to empty from a Zap.

One practical consequence worth calling out: you can stop using email addresses as your matching key. Emails change; a stable custom field like an account number doesn’t. Searches also now match on company name, deal stage, deal status, and customer status, which means search steps actually find the existing record instead of creating a duplicate. Cleaner data, without anyone doing data cleanup.

Three workflows to set up this week

Want more starting points? The Zapier templates for Pipeline CRM page has prebuilt Zaps you can switch on, and our earlier roundup of 10 Zapier automations that eliminate manual data entry still holds up, now with far more triggers to build on.

What do existing customers need to do?

Nothing. Every existing trigger, action, and search keeps its name and its fields, so existing Zaps keep running unchanged. You don’t need to reconnect your account. The upgrade happens behind the scenes, and the public Pipeline CRM listing on Zapier will show the expanded set of triggers and actions as the phased rollout completes. If you build Zaps regularly, the new options will simply appear in the editor.

How does this compare to other CRMs on Zapier?

On the things buyers ask about most, created and updated record triggers, deal stage and status changes, won and lost outcomes, and create and update actions for people, companies, deals, and activities, Pipeline CRM’s Zapier integration now matches the CRMs teams usually compare us against, including HubSpot, Pipedrive, Close, Copper, and Freshsales. And it leads in a few places:

• Delete triggers for keeping mirrored data accurate.
• A new-customer trigger and a convert-company-to-customer action.
• Updating calendar tasks and events, not just creating them.
• Uploading documents onto records from a URL.

The bigger point isn’t a feature checklist. It’s that “does Pipeline CRM connect to X” stops being a question: through Zapier, Pipeline CRM connects to thousands of apps, and the integration is now deep enough to automate around the whole life of a record.

Frequently asked questions