Connect Neon CRM

A step-by-step guide with pictures, from the Speakvora agent's own Connect tab.

Short answer: This connects your own Neon One account to your Speakvora agent. Then a customer can text where is order 1234 and get the answer in seconds, and the agent can send status and tracking texts. The agent only reads. It can never create, change or delete anything in Neon One. Only the status word and the order number are.

Every key, number and name in the pictures is a made-up example. Nothing here asks you to share a real key with anyone but the app on your own computer.

This connects your own Neon One account to your Speakvora agent. Then a customer can text *where is order 1234* and get the answer in seconds, and the agent can send status and tracking texts. The agent only reads. It can never create, change or delete anything in Neon One. Only the status word and the order number are ever texted back, never names, prices, items or addresses.

TIP: You need about 15 minutes, a computer, and the sign-in for your Neon One account (the owner or a manager). You can't break anything: if a step does not work, nothing has changed and you can just try again. The keys and screens below are made-up examples.

NOTE: This guide was written from Neon One's public developer documentation (a few details could not be confirmed) and has not been tried yet on a live Neon One account. If a screen looks different from what is described, press Connect, then Download report, and send it to support. We fix it for everyone.

Who this is for: nonprofit community. How Neon One gives access: You create the key yourself in your own account; no approval is needed. What it costs you: API access is not priced separately in the docs we read; Neon CRM plans start at about $99 per month.

Part 1. Get your key from Neon One

Do this on your computer, in a new browser tab, signed in to Neon One.

  1. Sign in to Neon CRM as an administrator.
  2. Click the Settings cog icon, then Organization Profile, and copy the Organization ID from Account Information.
  3. Go back to Settings and open User Management.
  4. Create a new user named Speakvora (a separate user for this integration) and give it only read permissions: Read Donation, Read Account, Read Event Registration.
  5. Turn on API Access for that user and save.
  6. Open the user again and copy the API key shown.
  7. Paste the Organization ID and API key into Speakvora.

WARNING: If Neon One asks which permissions to give, tick only the read-only ones: Read Properties, Read Donation, Read Account, Read Event Registration. Never give write or admin access.

TIP: To copy the key, click inside the box that shows it, press Command + C on a Mac or Ctrl + C on Windows (or right-click and choose Copy). Nothing will look different. It is now in your clipboard, ready to paste. Keep it private: anyone who has it can read your orders.

Part 2. Open the Connect tab in your agent

  1. Open your agent's dashboard (the page you open from the Start Speakvora Agent file).
  2. Press Connect in the menu. On a phone the menu is the bar along the top; slide it sideways if you do not see Connect.
  3. Step 1: press Connect (1)

  4. Under Your apps type Neon One in the box that says Find an app (1), or scroll down the list.
  5. Step 2: the Find an app box (1)

  6. Press Neon CRM. A card slides up. (If you only see apps for your own kind of business, that is on purpose: your agent only shows the systems that make sense for it.)
  7. Step 3: an app's card. The Full Guide button (1) opens this page.

Part 3. Paste it in

2 boxes to fill in. Click inside a box, press Command + V on a Mac or Ctrl + V on Windows, then move to the next:

  1. Neon organization ID. Settings (cog icon) > Organization Profile > Account Information > Organization ID.
  2. API key (secret: it stays on this computer and is never shown again, only the last few characters). Settings > User Management > open the Speakvora user > turn on API Access and copy the key.
  3. Part 3: each numbered box is one thing to paste. These are made-up examples.

TIP: Pasted by mistake into the wrong box? Click the box, press Command + A (Ctrl + A on Windows) to select all, then paste again.

Part 4. Test it

  1. Press the orange Save and test button.
  2. Neon One is asked for one harmless record, just to prove the key works. Nothing is changed in Neon One.
  3. Part 4: the green message under the buttons means it worked (1)

YOU SHOULD SEE: green words starting with Connected.

WARNING: Red words mean it did not work yet. Read them, then see If something is wrong below. Nothing bad happened.

What happens next

  • A customer texts something like where is order 1234. The agent answers *Your order 1234 is preparing.* (the status word from Neon One), or *I could not find that order. A team member will check and reply.*
  • Each person can ask five times an hour. If Neon One is down, the conversation carries on and the problem is written to Activity.
  • Mode: the agent asks Neon One when a customer asks.

If something is wrong

  • It says the key was refused (401 or 403): copy the key again from Neon One. Make sure there is no space before or after it, and that it is a live key for the right shop or location.
  • It cannot find an order (404): the number is not in Neon One, or Neon One uses a longer number than the one on the receipt.
  • It says too many requests (429): wait a minute and press Save and test again.
  • Neon One says you need a plan or approval: Base URL, Basic auth (organization ID as username, API key as password) and key creation are from Neon's official docs. The exact path and status field for reading ONE donation or registration by number were not readable in the docs page (it renders in the browser), so no order lookup is configured and the test path is not confirmed against a live account. Neon exposes GET /donations/{id} and GET /eventRegistrations/{registrationId}; confirm the status field before enabling.
  • Still stuck? Press Connect, then Download report, and email it to support. It never contains keys or customer messages.

If your plan has no API

  • Forward Neon CRM notification emails to the agent inbox instead.

Neon One's own instructions: https://developer.neoncrm.com/api-v2/

All help guides · Every agent feature · AI receptionist by industry

Questions

What if this happens: It says the key was refused (401 or 403)?

copy the key again from Neon One. Make sure there is no space before or after it, and that it is a live key for the right shop or location.

What if this happens: It cannot find an order (404)?

the number is not in Neon One, or Neon One uses a longer number than the one on the receipt.

What if this happens: It says too many requests (429)?

wait a minute and press Save and test again.

What if this happens: Neon One says you need a plan or approval?

Base URL, Basic auth (organization ID as username, API key as password) and key creation are from Neon's official docs. The exact path and status field for reading ONE donation or registration by number were not readable in the docs page (it renders in the browser), so no order lookup is configured and the test path is not confirmed against a live account. Neon exposes GET /donations/{id} and GET /eventRegistrations/{registrationId}; confirm the status field before enabling.

What if this happens: Still stuck??

Press Connect, then Download report, and email it to support. It never contains keys or customer messages.