Connect Salesforce Nonprofit Cloud / NPSP

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

Short answer: This connects your own Salesforce 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 Salesforce. Only the status word and the order number.

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 Salesforce 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 Salesforce. 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 Salesforce 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 Salesforce's public developer documentation (a few details could not be confirmed) and has not been tried yet on a live Salesforce 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 Salesforce gives access: The vendor connects through an authorised app. Follow the steps below to create or authorise it in your own account. What it costs you: REST API access depends on the Salesforce edition; the Power of Us program donates licences, and API availability on them was not confirmed.

Part 1. Get your key from Salesforce

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

  1. Sign in to Salesforce as a system administrator.
  2. Open Setup and search for App Manager.
  3. Create a Connected App (or External Client App), turn on OAuth settings, and select only the scope Manage user data via APIs (api).
  4. Create a dedicated integration user with a read-only profile or permission set for the objects Speakvora should see.
  5. Complete the OAuth flow for that user to obtain an access token.
  6. Open [[Setup > My Domain, and note your My Domain name]].
  7. Paste the My Domain name and the access token into Speakvora.

WARNING: If Salesforce asks which permissions to give, tick only the read-only ones: API Enabled, Read-only access to the records Speakvora should look up. 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 Salesforce 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 Salesforce Nonprofit Cloud / NPSP. 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. Your Salesforce My Domain name. The first part of the address you sign in to, for example your-nonprofit in your-nonprofit.my.salesforce.com.
  2. OAuth access token (secret: it stays on this computer and is never shown again, only the last few characters). Issued by a read-only Connected App or External Client App that your Salesforce admin sets up for Speakvora.
  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. Salesforce has no safe read-only check we can run, so nothing is called. The connection is used for real the first time a customer asks about an order, and any problem shows in Activity.
  3. Part 4: the green message under the buttons means it worked (1)

YOU SHOULD SEE: green words starting with Connected. (here: *Saved* and the sentence about the first customer)

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 Salesforce), or *I could not find that order. A team member will check and reply.*
  • Each person can ask five times an hour. If Salesforce is down, the conversation carries on and the problem is written to Activity.
  • Mode: the agent asks Salesforce when a customer asks.

If something is wrong

  • It says the key was refused (401 or 403): copy the key again from Salesforce. 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 Salesforce, or Salesforce 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.
  • Salesforce says you need a plan or approval: Salesforce only issues OAuth access tokens, which expire, and no simple long-lived key was confirmed. The official REST docs could not be read here (the pages returned 403), so no test or lookup call is set. Per-customer field mapping is also needed, because each nonprofit customizes objects and statuses.
  • 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

  • Ask Speakvora support to set up a read-only Salesforce report export instead.

Salesforce's own instructions: https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/intro_rest.htm

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 Salesforce. 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 Salesforce, or Salesforce 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: Salesforce says you need a plan or approval?

Salesforce only issues OAuth access tokens, which expire, and no simple long-lived key was confirmed. The official REST docs could not be read here (the pages returned 403), so no test or lookup call is set. Per-customer field mapping is also needed, because each nonprofit customizes objects and statuses.

What if this happens: Still stuck??

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