Connections
Integrations and API
Connect Spjallbox to your online store, CRM, accounting software and your own systems — with webhooks, an open API, or ready-made integrations.
Reading time · 7 min read
Besides email and social channels (covered on their own pages), Spjallbox offers integrations that pull data into the conversation panel or push data out of the system. All of them live under Settings → Integrations, and Settings → Developers for API keys and webhooks.
E-commerce and CRM
Shopify
Store domain (e.g. store.myshopify.com) + Admin API Access Token — shows a customer’s recent orders directly in the conversation.
WooCommerce
Store URL (HTTPS), Consumer Key and Consumer Secret — same idea as Shopify, for WordPress/WooCommerce stores.
HubSpot
Private App Access Token — shows a contact’s CRM details while an agent handles a case, and can push the contact to HubSpot as a lead.
Salesforce
Instance URL + Connected App Access Token — fetches contact and account details from Salesforce, and can create a Lead from a conversation.
Every integration is set up the same way: paste your keys/token into the relevant tab, click "Test connection" to confirm it can reach the service, then Save.
Leads from conversations
With HubSpot or Salesforce connected, a "Send to HubSpot" or "Send to Salesforce" button appears on the contact card and in the case context panel. The contact is marked as a lead in Spjallbox and created (or updated) in the CRM. An automation rule can do it for you too — e.g. mark everyone who asks for a "quote" as a lead and push them straight to HubSpot.
Accounting: Payday and dk
Connect Payday with an API Bearer Token and Company ID (optional) to see a customer’s invoices right inside the conversation — handy when a customer asks about an unpaid invoice without an agent needing to check a separate system.
Connect dk with a dkPlus API token to see the customer’s balance, credit limit, unpaid and overdue invoices and latest invoices next to the case. Lookup is by the company’s national ID first, then the contact’s national ID (e.g. from Kenni verification), then email. The token needs read access to customers and sales invoices.
Payday here is the accounting integration for information inside the conversation panel — don’t confuse it with Teya, the payment processor that handles Spjallbox’s own subscription charges on the Billing page.
Webhooks — sending data out
Under Settings → Developers → Webhooks you can register one or more URLs that receive a POST request every time something happens in Spjallbox. Choose which events should trigger the webhook:
- Conversation created
- Conversation updated
- Conversation closed
- Conversation resolved
- Conversation assigned
- New message
- 1
Add a webhook
Enter your URL (e.g. https://yourapp.com/webhooks/spjallbox) and check the events you want to receive.
- 2
Test it
Click "Test" to get a delivery immediately and confirm your endpoint responds.
- 3
Verify the signature (recommended)
Spjallbox signs every delivery so you can confirm on your end that it genuinely came from Spjallbox.
API channel — sending cases in from other systems
Under Settings → Developers → API channel you’ll find your secret key (starts with sk_…). Use it to send requests into Spjallbox directly from your own backend, without going through email or the web UI:
POST a request to /api/ingest with the header x-api-key and a JSON body containing name, email, subject and message — a new case appears instantly in the inbox.
Guard the secret key
The API key grants access to your inbox — keep it strictly server-side, never in code that runs in a customer’s browser.
Zapier, Make and n8n
The same API channel above can be used directly as an "HTTP request" step in Zapier, Make or n8n, so you can connect Spjallbox to almost any system without custom code — for example sending every new website form submission into Spjallbox, or the other way around: triggering an action elsewhere when a case is closed.
Do I need a developer to set up the integrations?+
The e-commerce and CRM integrations (Shopify, WooCommerce, HubSpot, Salesforce, Payday, dk) just need keys pasted in — no coding. Webhooks and the API channel are best suited to someone with developer access.
Can I rotate the API key if it leaks?+
Contact support to have a new key issued if the old one may have been exposed.
Is there public API documentation?+
The API channel and webhooks are documented directly on the Developers page with runnable examples — no need to look anything up externally to get started.