io.github.conquext/neuron

Connect an additional WhatsApp channel to a bot as a secondary number. The bot will respond to messages on this channel.

Add members to an existing group, resolved from any combination of sources (other groups, contact lists, contacts, pasted phones, all contacts). Address the group by its id, slug, or JID.

Add more unique codes/keys to a 'pool' code product's stock. Each buyer receives one. Returns the product with the new remaining count.

Add one or more contacts to a list by contact ID or phone number. Phone numbers without existing contacts are auto-created as minimal contact records.

Store or update a secret credential (API key, token, etc.) for a custom tool integration. Secrets are encrypted at rest.

Give a bot this persona's voice: merges a delimited voice block into the bot's system prompt (idempotent — re-applying or swapping personas replaces it cleanly) and tags the bot's metadata with the persona id.

Apply for seller access (digital products). Requires a Pro plan or higher; a platform admin then grants access.

Approve a bot-generated reflection to incorporate the learned insight into the bot's future behavior and responses.

Assign a bot to handle incoming messages on a specific WhatsApp channel. Replaces any previously assigned bot.

Assign a bot to handle interactions on a specific social media channel. The bot will be able to use the channel's credentials for social media actions.

Attach a knowledge base to a bot to enhance its responses with domain-specific knowledge. Optional priority determines retrieval order when multiple knowledge bases are attached.

Transcribe an audio recording and extract contact information (name, phone, email, notes, tags). Automatically saves the extracted contact to the organization's address book.

Block a WhatsApp contact. Blocked contacts cannot message the bot or see its profile.

Send a message to a bot via the API and receive a streaming or complete AI-generated response. Requires a valid API key with 'nrn_' prefix.

Retrieve configuration and status information about the bot associated with the provided API key.

Retrieve message history for a specific conversation with cursor-based pagination. Requires a valid API key.

Retrieve a paginated list of conversations managed by the bot. Supports filtering by conversation status. Requires a valid API key.

Send an outbound message through the bot API to a specified phone number. Supports text and media messages. Requires a valid API key.

Browse verified contact lists available in the shared marketplace pool. Filter by category, region, or search term.

Browse the shared marketplace pool of published bots, tools, knowledge bases, and reflections with optional filtering by type, category, tags, or search query.

Distill a reusable voice from a Collection of mined content: analyzes the top-engagement items and reverse-engineers a voiceProfile (tone, diction, cadence, emoji/formatting habits, themes, dos/donts) + representative exemplars. Requires the collection to have >=3 usable samples. Runs an LLM call (a few seconds).

Distill a reusable voice from an existing WhatsApp conversation's stored messages — no extension needed. `author` picks whose voice: 'me' (owner's own outgoing texts), 'contact' (the other party), 'bot', or 'any'. For a group chat, pass senderName/senderPhone to isolate one participant. Requires >=3 usable text messages. Runs an LLM call.

Distill a reusable voice from raw text — no Collection or browser extension needed. Feed it pasted posts, a chat/dialogue transcript, WhatsApp-export text, or your own well-crafted writing sample, and it reverse-engineers a voiceProfile (tone, diction, cadence, emoji/formatting habits, themes, dos/donts) + exemplars. Provide `text` (auto-split into samples) and/or `samples` (already-split). Runs an LLM call (a few seconds).

Enable or disable multiple built-in tools at once for a bot. More efficient than toggling tools individually.

Browse available campaigns in the marketplace that your organization can join to earn rewards by sending messages.

Retrieve all participants who have joined a campaign you own, including their delivery counts and earned rewards.

Cancel a still-pending approval (e.g. the upstream action was aborted). Fires the approval.cancelled callback. Requires a bot API key.

Cancel a confirmed or pending booking. Sends cancellation notifications to the invitee.

Cancel a running or waiting flow execution. Steps already completed are not rolled back.

Cancel a scheduled message to prevent it from being sent. Only messages with status 'scheduled' can be cancelled. This action cannot be undone.

Cancel the current active subscription. Access continues until the end of the current billing period.

Initiate a checkout session for a subscription plan upgrade. Returns a checkout URL or confirmation to complete the purchase.

Close an active conversation, marking it as completed. The bot will stop responding and the conversation is archived.

Mark a confirmed booking as completed (e.g. after the meeting has happened).

Compose and send a new message to a phone number via a specific channel. Automatically creates a new conversation if one does not exist.

Confirm a pending booking. Only works on bookings with status 'pending'.

Promote a phone-bearing lead into a contact (so it can be messaged / added to lists). Optionally add the new contact to a list.

Create an ad distribution request to send a message to contacts in pool lists matching target demographics. Deducts from wallet upon approval.

Create a new API key for programmatic access to a specific bot. Store the key securely as it cannot be retrieved later.

Create a new blog post. Body can be authored two ways: (1) `content` as markdown (GFM) + inline raw HTML, or (2) `blocks` — a structured array of typed layout blocks rendered as styled components (heroes, columns, callouts, code cards, embeds, CTAs, sanitized custom HTML). Prefer `blocks` for rich, magazine-style layouts; use `content` for simple prose. If both are given, `blocks` renders and `content` is kept as a fallback.

Create a new AI bot with specified name, model, and behavior instructions. Returns the created bot object.

Create a new broadcast message in draft status. Provide recipients directly or use recipientSources to resolve from contact lists. The WhatsApp channel is auto-resolved if not specified.

Create a new booking calendar with a name, timezone, and visibility setting.

Create a new outreach campaign with target audience, messaging template, and schedule configuration. Requires a Pro or Business plan.

Create a new WhatsApp channel with either Meta Cloud API or Baileys (direct WhatsApp) integration. Meta Cloud channels require metaPhoneNumberId and metaAccessToken.

Create a new contact in the organization's address book. If notes are provided, they are saved as a structured note entry with source tracking.

Create a new contact list. Slug is auto-generated from name if not provided. For dynamic lists, provide criteria with rules and/or an AI prompt.

Create a host-initiated event on a calendar. Supports attendees (with WhatsApp/email invitations), location, and daily/weekly/monthly recurrence.

Create a bookable event type on a calendar (e.g. '30-min consultation').

Create a new automation flow. A flow is a directed graph of nodes connected by edges. The graph MUST start with at least one trigger node (entry point). Edges connect nodes via output handles. BEFORE BUILDING: call neuron_get_flow_catalog and read its `reference` — it carries the JSON shapes you cannot guess: the ConditionGroup + operator list for branch/filter/switch conditions, the `cases`/`assignments`/`weekdays` composite shapes, the handle wiring map, and copy-ready `examples`. Condition `field` on a logic node must be a {{template}} (e.g. '{{trigger.text}}'); on a trigger's config.conditions it is a raw payload path (e.g. 'text'). AFTER SAVING: the flow always saves, but the response includes a `warnings` array flagging likely bugs (unknown node type, missing required field, malformed conditions/cases/assignments, edges wired to a handle a node never emits, missing trigger). Always check it and fix any warnings — a warning means that part will silently no-op at run time. TEMPLATE RESOLUTION: Node config values support {{…}} templates resolved at runtime: {{trigger.text}} — the triggering message text {{trigger.contactPhone}} — the sender's phone {{trigger.senderName}} — the sender's name {{vars.myVar}} — a variable set by logic.set_variable {{nodes.n_abc.output.text}} — output from a previous node {{= amount * 1.1 }} — inline expression (arithmetic, comparisons, ternary) ERROR HANDLING: Any node's config can include __errorHandling: { continueOnFail: true, retryCount: 3, retryDelayMs: 1000 } to retry on failure with exponential backoff and/or continue on the 'error' handle instead of failing the run. WIRING RULES: - logic.branch: 'true' and 'false' handles - logic.switch / logic.ai_router: one handle per case id, plus 'default' - logic.wait_for_reply: 'default' (replied) and 'timeout' - logic.wait_for_approval: 'approved', 'rejected', 'timeout' - logic.wait_first_of: 'reply', 'event', 'timeout' - logic.loop: 'loop' (body) and 'don…