Nucleus One Zapier integrationAutomate Nucleus One with Zapier.
The Nucleus One Zapier integration gives you 2 triggers, 3 actions and 0 searches. Enough to react when a project gains a document or a member, and to create tasks, submit forms or upload files from your other tools, with the real cost and the traps.
Verified Trustpilot reviews · AI, automation & growth agency
What the Nucleus One Zapier integration does
The Nucleus One Zapier integration connects Nucleus One, a cloud tool for running business processes, projects, tasks and documents, to the rest of your apps. You build a Zap: an automation with one trigger and one or more actions that runs each time the trigger event happens.
Three results come back most often. Onboarding that starts itself: User Added to a Project fires when someone joins a project, and New Task assigns them their first to-do. Files that file themselves: an attachment arriving in another app goes into the right project with Upload a Document, instead of sitting in an inbox. Requests that become processes: a form filled in elsewhere becomes a Nucleus One form with Submit a Form, so it sits in Nucleus One next to the forms filled in there.
Know this before you build: both Nucleus One triggers are polling triggers. Zapier checks for new items on a timer, every 15 minutes on the free plan, so a new document or member can take that long to show up in your other tools.
What Zapier does not do here: there is no search step, so a Zap can't look up a project, a user or a document by name. Every operation asks for an Organization ID and a Project ID that you type or map yourself. There's also no action to delete or move anything. Our Zapier review and the n8n vs Zapier comparison help you weigh the platforms.
Zapier vocabulary in one minute
Six words are enough for this page. Each is explained once, here, then used as is.
- Trigger
- The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it, for example a document added to a Nucleus One project.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something for you, such as creating a task in Nucleus One.
- Task
- The unit Zapier bills: one action your Zap completed successfully. Not to be confused with a Nucleus One task.
- Polling vs instant trigger
- Polling: Zapier checks the app on a timer. Instant: the app reports the event itself as it happens. Both Nucleus One triggers are polling ones.
- Filter
- A step that lets the Zap go on only when the incoming data meets your condition, and stops it otherwise.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A second action or a filter makes it one, and it then needs a paid plan.
What a Nucleus One Zap really costs
Nucleus One is not a premium app, so it works on the free plan. You pay in tasks, and only for actions that succeed.
- Free plan100 tasks a month, two-step Zaps
- TriggerCosts nothing
- Failed actionNot counted
- Check delaySet by your plan
The trigger never costs a task, and neither does Zapier checking Nucleus One for new items, however often it looks. Each successful action counts once: a Zap that creates a task and sends an email costs two tasks per run. A failed action is not billed. The free plan gives 100 tasks a month and unlimited Zaps, but each Zap stops at two steps, one trigger and one action. Your plan also sets how quickly the polling triggers notice new documents or members, as the grid shows.
Connect your Nucleus One account
- 01
Open your connections
In Zapier, open the Apps page of your account and click + Add connection. A connection is your Nucleus One account linked once, then reused by every step that uses Nucleus One.
- 02
Pick Nucleus One
Type Nucleus One in the search box of the dialog, select it, then click Add connection. A new browser tab then opens on the Nucleus One sign-in screen.
- 03
Sign in and grant access
Log in with your Nucleus One account and allow Zapier to use it. You need your own account, plus read or write access on the organizations and projects you don't own but want the Zap to touch.
Your first Zap: welcome new project members
GoalEach person added to a Nucleus One project receives an onboarding task and a welcome email.
- 01
Create the Zap
Start a new Zap, choose Nucleus One as the app that starts it and User Added to a Project as the event. Fill in the Organization ID and Project ID to watch.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent members of that project, so you map the next steps on a real person rather than an empty sample.
- 03
Create the task
Add New Task. Map the new member's email into User Email, then set the task name, description type and priority. All of them are required.
- 04
Send the welcome
Add your email app with a short welcome message. This second action makes the Zap multi-step, so it needs a paid plan; on the free plan, keep only the task.
- 05
Test, then publish
Test each step and read carefully what came back. Then click Publish to switch the Zap on for every member added from now on.
The 2 Nucleus One triggers
2 events start a Zap when something happens in Nucleus One. Zapier checks for them at the interval your plan allows.
Document Added to a Project
Polling triggerIn Zapier“Triggers when a document is added to a project.”
Starts your Zap when a new document lands in the Nucleus One project you point it at. Useful when a file arriving is the signal that work can start: a contract, an invoice, a signed form.
User Added to a Project
Polling triggerIn Zapier“Triggers when a user is added to a project.”
Fires when someone is added to a Nucleus One project. It turns a membership change into the start of an onboarding routine.
The 3 Nucleus One actions
Nucleus One gives you 3 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Upload a Document
ActionIn Zapier“Uploads a document to a project.”
Uploads a file into a Nucleus One project, under the name you choose and on behalf of a user.
Submit a Form
ActionIn Zapier“Submits a form.”
Submits a Nucleus One form, built from one of your form templates, in the name of a given user.
New Task
ActionIn Zapier“Creates a task for a user.”
Creates a task in a Nucleus One project and assigns it to a user identified by email.
When a Nucleus One Zap breaks
Zapier attaches no help article to Nucleus One, so the failures below are Zapier's general limits, applied to this app.
Each case below names the trap and how to avoid it. If a Zap still won't behave, our Zapier troubleshooting service picks it up.
Past documents never show up
A Zap only reacts to what happens after you switch it on. Documents and members already in the project stay where they are; moving that history is a separate job.The upload loop
Upload a Document into the same project that Document Added to a Project watches, and each upload starts the Zap again. It runs in circles and eats your tasks.A big batch is held back
A bulk import of documents can make a trigger return a huge batch at once. Zapier's flood protection may hold it back instead of running the Zap for each file.News arrives late
Both triggers are polled. On the free plan Zapier checks every 15 minutes, so a new member or document can wait that long. Zapier also never runs the same item twice.
Need help automating Nucleus One with Zapier?
A person reads every message.
