noCRM.io and Zapier: what syncs, what doesn't, and how to set it up
Zapier connects noCRM.io to other apps through 13 instant triggers and 16 actions and searches, centered on leads. noCRM's plan table lists integrations from the Expert plan up, not on Starter.
- Connector
- noCRM.io app in the Zapier app directory; the pages reviewed don't say who built it
- Sync direction
- Two-way through Zaps: noCRM.io events trigger other apps, and other apps' events create or update leads
- Setup time
- Not stated in the pages reviewed; the flow is account connection, one trigger, one action
- Availability
- noCRM.io Expert plan lists '3,000+ integrations & API', Starter does not; Zapier plan requirements not stated on the pages reviewed (Zapier has a free tier)
- Our rating
- 4 out of 5. 13 instant triggers and 16 actions and searches on leads, but noCRM's plan table lists integrations from Expert up, not on Starter.
| What | Direction | Detail |
|---|---|---|
| New, unassigned and assigned leads | noCRM.io → Zapier | Separate instant triggers fire when a lead is created, created unassigned, or assigned or re-assigned to someone. |
| Lead status and step changes | noCRM.io → Zapier | Two triggers fire when a lead moves to a status or a step you pick. Each needs that status or step name set in the trigger. |
| Lead edits, comments and deletions | noCRM.io → Zapier | Triggers fire when a lead's title or content changes, when someone comments on a lead, and when a lead is deleted. |
| Email received from a lead | noCRM.io → Zapier | An instant trigger fires when noCRM.io records an email from a lead. |
| Task status, client folders and prospects | noCRM.io → Zapier | One trigger each: a task reaches a chosen status, a client folder is created, a prospect is created in any prospecting list or a specific one. |
| Manual trigger | noCRM.io → Zapier | A user starts a Zap by clicking the lead's Actions menu. This suits cases where only some leads should go to another app. |
| Lead creation | Zapier → noCRM.io | Create Lead takes a title, description, user email, tags, creation date and step name. Create Prospect adds a prospect to a prospecting list. |
| Lead updates | Zapier → noCRM.io | Actions assign a lead, change its title, status or step, set amount and probability, set the estimated closing date, and add tags. |
| Comments, activities and attachments | Zapier → noCRM.io | Add Comment, Log an Activity and Add Attachment write to an existing lead. |
| Lead and prospecting list lookup | Two-way | Find Lead searches by email address. Find or Create Lead creates the lead when the search finds none. Find a Prospecting List searches by title. |
| Simplified API call | Zapier → noCRM.io | An action calls noCRM.io's simplified API for a lead or prospect ID and an API path, for anything the other actions don't cover. |
Setting it up
- Check that your noCRM.io plan lists integrations. Expert does; Starter does not.
- Create a Zap in Zapier and choose noCRM.io as the trigger app or the action app.
- Connect your noCRM.io account when Zapier asks. The pages reviewed don't say which credential Zapier requests.
- Pick the event, for example New Lead Status Changed To..., and set the status or step it should watch.
- Add the action in the other app, map the lead fields, and turn the Zap on.
Where the integration stops
- Integrations are plan-gated. noCRM's plan table lists '3,000+ integrations & API' under Expert and not under Starter. Check the plan before you design Zaps.
- Tasks and client folders have one trigger each. The listing shows a task-status trigger and a client-folder-created trigger, and no action that creates a task or edits a folder. The listing ends with a 'Load more' button, so confirm in the Zap editor.
- Change Status sets four values. It sets Standby, Won, Cancelled or Lost. Moving a lead between pipeline steps is a separate action, Change Step, which takes a step name.
- Lookups match on email address only. Find Lead and Find or Create Lead search by email, so a lead without an email address can't be matched this way.
- Zaps react to events; the listing describes no bulk sync. Existing leads are not copied to another app unless you build a Zap for them, for example with the manual trigger.
Zapier connects noCRM.io to other apps through event-driven Zaps. It suits teams that capture leads in forms, ads or spreadsheets and want them in noCRM.io, or want noCRM.io status changes to start work elsewhere.
The fact that most often surprises teams is the plan. noCRM's plan table lists integrations and API from Expert up, and Starter doesn't list them. Check your plan before you design anything. Plans and prices are on our noCRM.io pricing page.
Triggers cover the lead lifecycle
Zapier's noCRM.io listing has 13 triggers, and all are marked instant. They cover a new lead, an unassigned lead, an assignment, a status change, a step change, a comment, a deletion and an email from a lead.
Most triggers need little setup. Status and step triggers ask for the status or step name.
The manual trigger gives you control. A user clicks the lead's Actions menu, and only then does the Zap run. Use it when only some leads should go to another app.
Actions edit one aspect of a lead at a time
Writing back is granular. Separate actions assign a lead, change its title, move it to a step, set its status, set amount and probability, and set the estimated closing date. Others add comments, tags, attachments and logged activities.
Create Lead is the entry point for form and ad capture. It takes a title, description, user email, tags, creation date and step name.
Find or Create Lead searches by email address first. That prevents duplicate leads when the same person submits twice. It also means leads without an email address can't be matched.
Tasks and client folders get less. The listing shows one trigger for each and no action that creates a task or edits a folder. The listing has a "Load more" button, so check the Zap editor before you rule an action out.
What the pages don't say
The pages reviewed leave four things open. They don't say whether noCRM.io or Zapier built the app. They don't say which credential Zapier asks for when you connect, or how long setup takes. They also don't state Zapier's plan requirements.
For anything the actions don't cover, the Call Simplified API action reaches noCRM.io's simplified API from inside a Zap. If you need native email logging instead, see our noCRM.io and Gmail review. For context on the product, see the noCRM.io vendor page and our Zapier integrations page.