Nodes Reference

Nodes are the building blocks of a workflow. Each node has a stable type ID (e.g. core.http), a kind (action or trigger), and a set of properties that configure its behavior. This section documents every node in the built-in catalog, including the full property list and the possible values each property can take.

How to read a node page

Every node page follows the same shape:

• Type ID - the string you reference in a workflow (type on a step). This is the value registered in the node catalog.
• Kind - Action nodes transform data mid-workflow; Trigger nodes start a workflow.
• Ports - how many inputs and outputs the node has, i.e. how many edges you can connect to and from it. Almost every node takes one input and emits one output; root triggers take none, and core.if emits two outputs (true, false) instead of one.
• Credentials - the credential the node binds to, or None if it doesn't call out to an external service.
• Properties - a table of every parameter: its key, type, whether it is required, its default, and the possible values.

Property types

Properties use one of these types:

Type	Meaning
string	Free text. Supports expressions unless noted.
number	Numeric value.
boolean	true / false.
options	A single choice from a fixed list (the Possible values column lists every option).
array	A repeating collection of nested fields.
object	A key/value map of nested fields.
dateTime	An ISO date-time or expression.
checkbox	A multi-select set of toggles.
resourceMapper	A column/field mapping for an external resource.
credential	A reference to a stored credential.
file	A binary file reference.

The Applies when column tells you when a property is actually in effect - it's only read (and, if required, only required) when the listed parameter holds one of the listed values. This isn't a UI-only concern: in Culvii Kit you can set any property in code, but a property with a condition here has no effect unless that condition holds. For example, on the HTTP Request node, bearerToken is only used when authentication is set to bearerToken; setting it with authentication left at none does nothing. Properties marked Always are in effect regardless of other property values. A value of Loaded dynamically at runtime means the choices are fetched live (for example, the list of SharePoint sites) rather than fixed in the node definition.

Action nodes

Node	Type ID	Credential	Summary
Agent	core.agent	None	Delegate a task to a multi-agent run and wait for the result.
If	core.if	None	Route items into a true/false branch based on conditions.
Set	core.set	None	Create or overwrite fields on the output item.
HTTP Request	core.http	None	Make an outbound HTTP request.
Code	core.code	None	Run custom JavaScript against the workflow data.
JWT	core.jwt	None	Sign or verify a JSON Web Token (HS256).
Browser Automation	core.browserAutomation	None	Drive a headless browser through a sequence of steps.
Wait Timer	waitTimer	None	Pause the workflow for a fixed duration.

Trigger nodes

Node	Type ID	Credential	Summary
Manual Trigger	manualTrigger	None	Start a workflow manually with an optional payload schema.
Cron Trigger	cronTrigger	None	Start a workflow on a cron schedule.
Webhook Trigger	webhookTrigger	None	Start a workflow from an inbound HTTP request.
Gmail Trigger	gmailTrigger	Gmail	Poll Gmail for new/matching messages.
Outlook Trigger	microsoftOutlookTrigger	Microsoft Outlook	Poll Outlook for new/matching messages.
Slack Trigger	slackTrigger	Slack	Poll Slack for new messages in a channel.

Connector nodes

Node	Type ID	Credential	Summary
Gmail	gmail	Gmail	Send and read Gmail messages.
Google Calendar	googleCalendar	Google Calendar	Create and read calendar events.
Google Docs	googleDocs	Google Docs	Create, read, and edit documents.
Slack	slack	Slack	Send messages to channels, groups, and users.
Outlook	microsoftOutlook	Microsoft Outlook	Send and read Outlook messages.
SharePoint	microsoftSharepoint	microsoftOAuth2	Read and write SharePoint list items.
S3	s3	aws	Upload and retrieve objects in Amazon S3.