Neuron parts

The settings of each neuron stage - START, GET, DO, MAKE and SEND - and what each one does.

Each neuron has five stages: START, GET, DO, MAKE and SEND. Click a stage on the neuron card to open its tab in the settings panel. One neuron can take several inputs in GET and send to several places in SEND, but it has one set of instructions and makes one result per run. Use more neurons when a task has more than one AI step.

START: when the neuron runs

The START tab opens with a RUNS WHEN sentence that sums up everything that starts the neuron, followed by one row per way to start it:

Play: runs once when you press it.
Schedule: runs at a set time: a countdown, an alarm or a recurring schedule. See Scheduling.
Other neurons: starts after another neuron. See Connections.
Webhook: starts from your own systems with a webhook call and a key.
App events: starts when something happens in a connected app. See App connections.

Click a row, or its Set up link, to open its settings. The Play row has its own Play button.

START: Play and Test this neuron only

Under Run now in START:

Play runs this neuron and every neuron connected after it.
Test this neuron only (shown when other neurons come after this one) runs just this neuron. Nothing is sent, nothing is saved to memory, and the neurons after it don't start.
Play through the queue (shown when an input has queued values) runs the neuron once for each queued value, one after another.

START: Webhook keys

The API webhook & keys settings let your own systems start the neuron with a web call.

In START, open Webhook. It shows the webhook address your systems call.
Click New key, type a Key name, and optionally set Expires (optional).
Click Create key.
Click Copy secret and store the secret somewhere safe. It is shown only once.
Click Done.

A call needs a key to start the neuron. To stop a key working, click Revoke key. See Webhook integration for how to make the call.

GET: add and change inputs

GET holds the neuron's inputs. Each input has a name, a type and a value.

Click Add input. A new neuron already has one text input, "Text Input 1".
Type a name in the name field, next to the type button.
Click the type button (it shows the current type, such as Text) and pick Text, PDF, Image, Audio file, Voice recording or Table. See Data types.
Choose where the value Comes from (see "GET: where a value comes from" below), then fill it in: type the text, upload a file, record audio, or pick a table.

To remove an input, click Remove input. Changing an input's type clears its current value, so the app asks you to confirm in Change input type with Change type first.

GET: hints and Required

Add a hint: a short hint shown to whoever runs the neuron, such as a User running your agent.
Required: the run waits until this input has a value. Required inputs show REQ on the neuron card.

GET: where a value comes from

Each input has Comes from:

Ask when run: when you press Play, you're asked for the value before the run starts. When the neuron runs later in a flow, or from a schedule, an app event or a webhook, the run waits at this neuron and shows Waiting for you on it, in a notice with Answer, and in Runs. Answer there and the run goes on. Set Default value to prefill the question; it is used as the answer if none comes within Wait for an answer, which can be from 5 minutes to 24 hours (the default is 24 hours). With no answer and no default, the neuron stops with "No answer given" and its On error link runs. Stop run cancels a waiting run. A neuron waits for one answer at a time.
Set in advance: the value you type or upload here is used on every run. Add more values (a blank line between values adds several) to make a queue: each run uses the top one, and the last one stays.
Another neuron: the value comes from another neuron's input or result. Pick it from the list; Change picks another, the clear button removes the link. Until that neuron has run, there is nothing to preview.

People using your agent are never asked: in an agent, an input set to Ask when run uses its default value.

GET: queue several values

A queue lines up several values for one input. Each queued value becomes its own run, one after another.

On the input, keep Comes from on Set in advance.
Add values: type them and click Add, Add 2 values or Add to queue (a blank line between values adds several at once), or upload several files with Upload files to queue. The queue starts when the input has a second value.
Press Play through the queue in START, or Play all queued in the neuron's menu.

Click Turn off queue to go back to one value; this clears the queued values, and the tooltip tells you how many. Only one input per neuron can take a queue. An input that asks when run, or that is filled by another neuron or by the webhook, can't take a queue, because it takes one value at a time. To remove a queued value, click Remove from queue.

GET: inputs filled by another neuron or the webhook

An input whose Comes from is Another neuron takes the value of one of the neurons before it. An input that receives a linked value from a connection reads Another neuron too, and you change it in the connection's settings.

When you connect a neuron to this one, a Connection input appears, named after the parent (for example "Connection input (from Neuron 35c)"). It shows FROM CONNECTION and "Filled by the parent neuron on each run." An input the webhook fills shows FROM WEBHOOK. An input that receives a linked value from a connection shows LINKED and "Filled by a connection from" the parent. These inputs are read-only: change what they get in the connection's settings. See Connections.

GET: what Users of your agent can do with an input

When you publish the workflow as an agent, People using the agent sets what a User can do with each input:

Can change: the User fills it in or changes it.
Can see: the User sees your value but can't change it.
Hidden: the User doesn't see it; your value is used.

DO: how DO works

At the top of DO, How DO works picks how the neuron does its work:

AI: a model follows your instructions.
Steps: fixed steps such as filtering rows or filling a template, with no AI.
Code: your own code, with no AI. See Code.

Switching keeps what you set in the other modes, so you can switch back.

DO: instructions

Instructions tell the AI what to do with the inputs. Brief it like a colleague: what to look at, what to produce, what to flag. You can also edit instructions right on the card (Click to edit).

Example instructions:

"Summarise this document in three bullet points."
"Pull out every email address and phone number."
"Translate this text into Spanish."
"Write a polite reply to this email."

For some pairs of input and result types, the work happens automatically and DO shows DO isn't used here: instructions are ignored. Others show DO is optional here. Instructions can include references to Memory. See References.

Prepare input, at the top of the Instructions box, runs optional steps before the AI sees the input, for example filtering a long table down to the rows that matter. It says how many steps run when you have set some.

Under the instructions, three checks turn green as you write: Mentions an input, Says what to make and Sets limits. NEEDED shows while the instructions are too short to be useful.

DO: web search on Auto

On Auto, a run searches the web when the instructions or the input use one of these words or phrases, as whole words: research, latest, news, current, recent, today, now, real-time, live, web search, search the web, find information, look up, what happened, stock price, weather, breaking news, update on, search for, find out, what is happening, current events, right now, this week, this month.

It also searches when a question asks for the latest or current information, or when the text names a year such as 2026 or says this year, last year, yesterday or tomorrow.

To make every run search the web, add the Web search tag: type {{ in the instructions and pick Web search under Tools, or click Add web search above the box when it offers it. The tag shows as a Web search chip; delete the chip to turn it off. When it appears as {{web-search}} (for example on the classic canvas), it works the same way.

Add web search appears just above the instructions when they use one of the words above, or ask a question about the latest information, or name a year, and the tag is not there yet. Dismiss (the x) hides it for that neuron in this browser; it comes back when the instructions gain a new such word.

A run that searches the web uses a stronger model and costs more credits than one that doesn't. Web search works only with Auto, and not while Apps are picked; the chip is grey and says why when it won't be used. It applies when the neuron makes text from text, and to decisions.

DO: the settings row

Under How DO works, a row of buttons shows DO's settings. Click one to open it; click it again or Close to put it away.

Model (AI only): which model follows your instructions. Auto is the default: it picks for you, and it is the only choice that can search the web: it does when the instructions or the input ask for current information, or when the instructions have the Web search tag (see DO: web search on Auto). Or pick a model by family: GPT (GPT-6 Luna, GPT-6.1 Sol, GPT-6 Astra), Gemini (Gemini 3.5 Flash-Lite, Gemini 3.8 Flash, Gemini 3.1 Pro (preview)) or Claude (Claude Haiku 5.5, Claude Sonnet 5.5, Claude Opus 5.5). Every model can use apps and understand images; none of the named models searches the web. Under the list, each ability shows as a tag, and one a model lacks is crossed out; pointing at it says why. The model changes what a run costs: smaller models use fewer credits, larger ones handle harder work. See Credits & usage to see what your runs spent.
Apps (AI only): the connected apps this neuron may use, and which of their actions. With an app open, Search actions… filters its actions by name or description. Max tool rounds per run sets how many rounds of app actions one run may make, up to 10 rounds. See App connections.
Memory: what this neuron recalls from Memory each run. Also shown for Steps and Code. See Memory.
Documents (AI only): whether DO may reach any table or doc in this workflow by name.

The model you pick stays with the neuron when you publish it as an agent; people using the agent don't see it.

MAKE: the kind of result

Active output sets what the neuron produces on each run, one type at a time: Text, Image, Audio, Table or Decision. Which types you can pick depends on the inputs. Changing the type clears the current result, so the app asks you to confirm with Change type first.

Quick-switch on the canvas shows chosen result types on the card, so you (or Users of your agent) can switch the result type without opening the settings.

MAKE: decisions

A Decision result picks one of several paths. Use it to send different cases to different neurons.

In MAKE, choose Decision.
Under Decision conditions, give each condition a Condition name and a Condition description that says what it means. Click Add condition for more.
Connect each condition to the neuron that should run when it is picked: each condition has its own connector on the right edge of the card. Click it, then click another neuron's receptor.

On each run the neuron picks exactly one condition, and only the neurons connected to that condition run.

MAKE: the last result

Last output in MAKE shows the latest result. Preview text, play audio, or view and download an image or table. On the card, View full output opens the whole result.

SEND: destinations

Destinations sets where the result goes. Pick as many as you need; each gets the same result.

Neuron Out: pass the result to a connected neuron. See Connections.
Email: under Email to, add the addresses to send the result to. Adding an address turns email on.
Telegram: under Telegram chat, type the chat ID or an @channel. To find your chat ID, send /start to the Neuron bot (the link is under the field) and paste the chat ID it replies with.
API: under Endpoint URL, type the address that should receive the result. It must start with https://, http:// or /. It is saved when you leave the field, and clearing it turns API off.
Document: writes rows to a table in this workflow. MAKE must be set to Table. See Documents.
Dashboard: sends the result to the feeds of a dashboard in this workflow, so the dashboard shows the latest data. Pick a dashboard and a feed, then Add. See Dashboards.

SEND: On error

The On error box in SEND shows which neurons start if this neuron fails. See On error links.

Limits

Inputs per neuron: up to 3 inputs.
Text input: up to 50,000 characters.
Input hint: up to 500 characters.
Instructions: up to 10,000 characters.
File upload: up to 32 MB per file.
Text files and spreadsheets: read in full, up to 200,000 characters of text; a longer file stops the neuron with a message to try a shorter file or split it into parts. Older Excel files (.xls), OpenDocument spreadsheets (.ods) and password-protected Excel files can't be read: save them as .xlsx or CSV first (and remove the password), then add them again.
Decision conditions: at least 2 conditions.
Email recipients: up to 5 recipients.
Email text: up to 5,000 characters in the email body; a longer result is attached as a file, up to 25 MB.
Telegram message: up to 4,096 characters.

Common problems

A webhook key's secret is lost

A webhook key's secret is shown only once, when you create the key. If you lose it, click Revoke key and create a new key.

The API endpoint URL is not saved

The API endpoint URL must start with https://, http:// or /. Otherwise the field shows "Not saved." Fix the address and leave the field to save it.

Telegram messages don't arrive

Check the Telegram chat ID. Send /start to the Neuron bot again and paste the chat ID it replies with. For a channel, use its @name and make sure the bot can post there.

Queue can't be turned on for an input

Only one input per neuron can take a queue, and an input that asks when run, or is filled by another neuron or the webhook, can't take one. Click Turn off queue on the other input first.

Document is greyed out in SEND

The Document destination writes rows to a table, so it needs a table result. Set MAKE to Table first.