Resources · Zapier integration

Nuclia Zapier integrationAutomate Nuclia with Zapier.

Nuclia Zapier integration: 0 triggers, 3 actions, 0 searches. Zapier can feed files, web pages and YouTube videos into your Nuclia knowledge box for AI search. It cannot start anything from Nuclia, so another app always fires first.

See the 3 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Nuclia Zapier integration actually does

The Nuclia Zapier integration is a one-way pipe into your knowledge box. Something happens in another app, Zapier picks it up, and Nuclia receives a file, a page or a cloud file to index. Nuclia then handles the transcription, the text extraction and the parsing, so the content becomes searchable without anyone uploading it by hand.

Three results you can get from it, each tied to a real action:

A searchable copy of every new document. Index File takes a file handed over by an earlier step and adds it to the knowledge box. Because it keys on a unique ID you choose, sending the same document again replaces the old version instead of creating a twin.

A library of pages and videos you care about. Index Page only needs a URL. Point it at a web page or a YouTube video and Nuclia processes it, transcript included for the video.

Files that stay where they live. Index a Cloud-Based File works from a link to a file stored online, plus its original name, so the file itself never travels through Zapier.

What Zapier does not do with Nuclia: it cannot react to anything happening inside Nuclia (there is no trigger), and it cannot look up a resource that is already indexed (there is no search). Querying the knowledge box, reading answers back or deleting a resource are not on the menu either. If your plan relies on one of those, check the n8n vs Zapier comparison before you build.

Vocabulary

Zapier vocabulary in one minute

Seven words come back on every line of this page. Here they are in plain English.

Zap
The automation you build: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event in an app that starts the Zap. Nuclia has none, so the trigger always comes from another tool.
Action
What the Zap does once it has started: the step that writes, sends or moves something for you. Here, the indexing.
Task
The unit Zapier bills: one action your Zap completes successfully. Your plan's allowance is a count of those.
Polling vs instant
A polling trigger is checked on a timer. An instant trigger is pushed by the app the moment the event happens.
Filter
A step that lets the Zap carry on only when what arrived meets your condition, and stops it otherwise.
Connection
Your Nuclia account linked to Zapier once, then reused by every step that talks to Nuclia.
Cost

What indexing into Nuclia costs you on Zapier

Nuclia is not a premium app, so it works on the free plan. The bill is counted in tasks, and only the Nuclia step counts.

  • Free plan100 tasks a month, unlimited Zaps
  • Free plan Zap size2 steps: one trigger, one action
  • Premium appNo, Nuclia runs on the free plan
  • CountedEach successful Nuclia action

The trigger in the other app never costs a task, however often Zapier checks it for new items. Each successful index call costs one task, and a call that fails costs nothing. The catch is the free plan: it builds Zaps of two steps only, one trigger and one action. Add a filter (say, only PDFs) or a second Nuclia step and the Zap becomes multi-step, which needs a paid plan. Polling triggers are also checked less often on Free, as the grid below shows.

Connect

Connect Nuclia to Zapier in 3 steps

  1. 01

    Open your connections

    In Zapier, go to Apps, the page that lists every account you have linked. Click + Add connection, type Nuclia in the search box of the dialog and pick it from the results.

  2. 02

    Sign in to Nuclia

    Click Add connection. A new tab opens on Nuclia: log in with the account that owns the knowledge box you want to fill. You need an account on Nuclia first, Zapier cannot create one for you.

  3. 03

    Grant access

    Approve the access request in that tab. The connection then shows up in your list and every future Nuclia step reuses it. If the knowledge box belongs to a colleague, make sure your account can write to it.

First Zap

Your first Nuclia Zap, step by step

GoalEvery file dropped into a shared Google Drive folder lands in your Nuclia knowledge box, ready for AI search.

  1. 01

    Create the Zap

    Start a new Zap in the editor. Pick Google Drive as the app that starts things, the folder event as the trigger, and the shared folder your team drops files into.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent files of the folder, so you can pick a real one to map the next step from.

  3. 03

    Add the Nuclia action

    Add a step below the trigger, choose Nuclia as the app and Index File as the event, then select the Nuclia connection you created in the previous section.

  4. 04

    Map the four fields

    Use the Drive file ID for UID, its name for Title and Original Filename, and the file itself for File. The stable ID is what lets a later edit replace the old copy.

  5. 05

    Test and publish

    Test the Nuclia step once and check that the document now appears in the knowledge box. If it does, click Publish to switch the Zap on for good.

Actions

Nuclia actions on Zapier

Nuclia gives you 3 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Index File

Action

In Zapier“Indexes a file in your knowledge box. If the file was already indexed (according the unique id field), it will be re-uploaded and reprocessed.”

Pushes a file from an earlier step into your knowledge box so Nuclia can parse it and make it searchable. Send the same UID twice and Nuclia uploads and processes it again rather than keeping two copies.

When to use it
a contract, a slide deck or a recorded call lands in a storage app and should be findable by your AI assistant without anyone uploading it.
Watch out
a UID that changes at each run (a timestamp, for instance) defeats the replacement and fills the box with duplicates.
2

Index Page

Action

In Zapier“Indexes a page (a web page or a YouTube video) in your knowledge box. If the page was already indexed, it will be reprocessed.”

Hands Nuclia a single URL, either a web page or a YouTube video, and lets it fetch and process the content. If that URL is already in the box, it gets processed again with its current content.

When to use it
your team saves useful articles or product demos in a spreadsheet or a chat channel, and you want each new link searchable without copying text.
Watch out
the URL is the one required field, so text around the link leaves Nuclia nothing clean to open.
3

Index a Cloud-Based File

Action

In Zapier“Indexes a remote file in your knowledge box. If the file was already indexed, it will be reprocessed.”

Indexes a document that sits online, from its link and its original filename, without Zapier carrying the file across. Sending a link that is already indexed triggers a fresh round of processing.

When to use it
the earlier step only gives you a download link, not the file, and you still want the document in the knowledge box.
Watch out
the original filename is required too, so a trigger that hands over a bare link with no name stops this step.
When it breaks

When the Nuclia Zap breaks

Zapier attaches no help article to Nuclia, so the failures below come from how Zaps work in general and from what the three actions say about themselves.

Most surprises happen on day one, when people expect the archive to follow, or on the day a bulk import hits the trigger folder. When in doubt, the Zapier troubleshooting guide walks through the usual checks.

  • The archive never shows up

    A Zap only reacts to what happens after you switch it on. The files already in the folder stay out of Nuclia: moving that backlog is a separate job.

  • A bulk import stalls

    When the trigger app suddenly returns a huge batch, after a migration for example, Zapier's flood protection can hold the run back before anything reaches Nuclia.

  • The same file never runs twice

    On a polling trigger, Zapier remembers what it has already seen, so the same file never starts the Zap twice or costs a second task.

  • Duplicates in the knowledge box

    Index File replaces a document only when the UID matches. Map a value that changes on every run and each new pass adds another copy instead.
Need help

Need help automating Nuclia with Zapier?

A person reads every message.

FAQ

Nuclia Zapier integration: common questions

01Is the Nuclia Zapier integration free?
Yes, on the free plan, because Nuclia is not a premium app. That plan gives you 100 tasks a month and unlimited Zaps, but each Zap is limited to two steps: one trigger in another app, then one Nuclia action. The moment you add a filter or a second action, the Zap becomes multi-step and needs a paid plan. Your own Nuclia subscription is a separate matter, and this page does not cover it.
02How many tasks does indexing a file into Nuclia use?
One task per successful Nuclia action. The trigger in the other app is free, and so is every check Zapier makes for new items. If an index call fails, it is not counted. A Zap that indexes one file per run therefore uses one task per file, while a Zap with two Nuclia steps would use two. Zapier notes that a few apps and actions cost more than one task, so keep an eye on your count after the first runs.
03Does Nuclia index content in real time through Zapier?
It depends entirely on the app that starts the Zap, since Nuclia has no trigger of its own. With an instant trigger, the other app warns Zapier as soon as the event happens and Nuclia gets the content straight away, whatever your plan. With a polling trigger, Zapier checks on a timer: every 15 minutes on Free, 2 on Professional, 1 on Team and Enterprise. Pick an instant trigger when speed matters.
04What do you need to connect Nuclia to Zapier?
An existing Nuclia account with access to the knowledge box you want to fill, plus write rights if that box belongs to someone else. Zapier does not create the Nuclia account for you. The connection takes three moves: open Apps in Zapier, click + Add connection and pick Nuclia, then sign in and approve the access request. After that, every Nuclia step in every Zap reuses the same connection without asking you to log in again.
05Why does Nuclia keep creating duplicate documents?
Because the UID field changes from one run to the next. Index File decides whether a document is new or a replacement by that unique ID: same UID, Nuclia uploads and reprocesses the existing entry; different UID, it creates a new one. Map a value that never moves, such as the file ID from the storage app, rather than a name or a date, and edits will replace the old copy.
06What if the Nuclia operation you need is not on Zapier?
Then Zapier cannot do it for this app today. Its three actions only add content to a knowledge box: a file, a page or video by URL, or a cloud file by link. Querying the box, reading results back, deleting resources or reacting to events inside Nuclia are not offered. A tool that talks to Nuclia directly is the usual way around that, and it deserves a comparison before you commit.
07Zapier, Make or n8n for Nuclia?
Judge on three criteria rather than a ranking. Coverage: on Zapier, Nuclia offers three indexing actions and nothing else, so anything beyond ingestion needs another route. Cost model: Zapier bills each successful action as a task, which is easy to predict for a one-file-one-run flow. Control: if you need to query the knowledge box or handle responses, a tool that talks to Nuclia directly fits better. Start from the operations your flow actually requires.
Same platform

Other docs you might need on this stack.

Browse all integrations