Nexus Intake
Nexus Intake adds to the Nexus CRM the contacts that come in through other channels and records what they do. With a single component you work with two things: contacts (leads), with their details, their consent and the campaign they come from, and a contact’s events, such as a form submitted, a download or attending a webinar.
Nexus takes care of the rest: it removes duplicates, stores the consent and classifies each contact automatically.
When to use it
- Every contact form on your website must enter Nexus as a lead.
- A chatbot or a voice agent collects a visitor’s email and you want to save it in the CRM.
- You have a list of contacts in a spreadsheet and want to import it without creating duplicates.
- You want Nexus to know that a contact has downloaded a guide or attended a webinar.
Configuration
You need a Nexus credential with your Nexus address (for example https://nexus.your-company.com) and an application key that starts with nxa_live_. See Credentials.
A Nexus administrator creates the key in Administration › Integrations › API keys, with New API key. Choose NappAI CMS website in What it is for: it includes the Contacts permission. To send events, also tick Events in What it can send. When it is created, Nexus shows the API key and the Nexus address: they are the two pieces of the credential. The key is only shown once.
| Field | What it does |
|---|---|
| Credential (required) | The Nexus credential. It fills in Nexus address and Nexus API key for you. |
| Resource | What you work with: Contacts or Events (a contact’s events). Default: Contacts. |
| Operation | What you do. The list changes with the chosen Resource. See Resources and operations. |
| Idempotency key (advanced) | Optional. If you repeat the same key within 24 hours, Nexus doesn’t do the write again. Put here the ID of what comes in, for example the form submission’s, so a retry doesn’t add it twice. |
Resources and operations
Contacts
| Operation | What it does | Fields |
|---|---|---|
Create Contact | Sends a lead to Nexus with its details, its consent, the page it comes from and its campaign. | Email. Optional: First name, Last name, Phone, Company, Job title, Website, Message, Source, External ID, Marketing consent, Page URL, Form name, UTM (JSON) and Custom fields (JSON). |
- Message is what the person wrote, up to 4,000 characters.
- Source says where the lead comes from, for example
web_form,nappaiorchatbot. Default:api. - External ID is the lead’s ID in the system it comes from.
- Marketing consent:
Not stated(the default) sends nothing and Nexus keeps what it already knew;Yesonly if the person agreed to receive marketing communications;Noif they refused. - Page URL and Form name are the page and the form where it was filled in.
- UTM (JSON) is the campaign data, for example
{"source": "google", "medium": "cpc", "campaign": "demo"}. - Custom fields (JSON) is extra data, for example
{"plan": "pro"}, up to 8 KB.
Events (a contact’s events)
| Operation | What it does | Fields |
|---|---|---|
Create Event | Records in Nexus something a contact did. | Event type, and Email or External ID. Optional: Custom type, When and Properties (JSON). |
- Event type can be
form_submitted(default),page_view,download,webinar_attendedorcustom(your own). - Custom type is only used with
custom: a lowercase name, for exampletrial_started, which is sent ascustom.trial_started. - Email or External ID identify the contact: use the same one you sent it with.
- When is the event’s date and time, for example
2026-11-09T10:30:00Z. If you leave it empty, the current moment is used. - Properties (JSON) are the details, for example
{"file": "crm-guide.pdf"}, up to 4 KB.
Output
The Data output returns Nexus’s answer. When creating a contact, Nexus replies with its intake ID (intake_id) and the RECEIVED status: it processes it in about 30 seconds and, if the contact is new, fires the contact.created event, which you can pick up with Nexus Webhook.
The component supports Batch Mode, to send one contact for each item of a list, and it can be connected to an Agent as a tool. See Tools.
Example
A company wants every demo request from its website to enter Nexus.
- The form reaches the flow through a Webhook Input with the name, the email, the company, the message and whether the person agreed to receive communications.
- Add Nexus Intake with the
Contactsresource and theCreate Contactoperation. - Take each value of the form to its field: Email, First name, Company, Message and Marketing consent. In Source type
web_formand in Form name,Demo request. - In Idempotency key, in the advanced settings, put the ID of the form submission, so a retry doesn’t add it twice.
Good practices
- Don’t make up emails or consents: consent is only true if the person agreed to it.
- Check that UTM (JSON), Custom fields (JSON) and Properties (JSON) are valid JSON. If not, the component stops with an error and sends nothing.
- As a chatbot tool, let the agent fill in the visitor’s email and name, and fix Source yourself.
Security and limitations
- The Nexus key can only send data: it can’t read the CRM. To look up contacts or deals, use Nexus CRM.
- Nexus only stores the events of contacts that came in with the same key and are already processed. It drops the rest without warning: Nexus replies with the events received, not the ones stored.
- That’s why you shouldn’t send an event right after creating the contact in the same run: wait until Nexus has processed it.
- If Nexus rejects the key, it may be revoked, paused or missing the permission needed. An administrator can check it in Administration › Integrations.
- Nexus limits the number of writes per minute. If you go over it, the component tells you how many seconds to wait.
Related components
- Nexus Marketing: content resources, web analytics and SEO audits.
- Nexus CRM: read and update the CRM as a person.
- Nexus Webhook: starts the flow with what happens in Nexus.