Why integrations matter
FN
Finn Osei · Finance Operations Lead
"The moment a deal closes, our finance system needs to know immediately so invoicing can start. Nobody should have to manually retype closed deals into a second system — that's exactly how numbers drift apart."
Almost every business runs more than one software system — a CRM, a finance tool, a support tool, and so on. An integration is a connection that lets two systems talk to each other automatically, without a person copying data between them by hand.
What this means for you
Closed deals reach other systems the instant they close. Data from outside systems lands in the CRM automatically too — with a full log of what was sent and received, for troubleshooting.Anatomy of the integration layer
Data can flow two ways: outbound (SmartLite sending data out to another system) and inbound (another system sending data into SmartLite). Each direction has its own tools:
| Direction | Tool | Use case |
|---|---|---|
| Outbound | API Keys — a secret password-like code, scoped to specific permissions (READ / WRITE / DELETE / BULK / ADMIN) | Let an external system securely ask SmartLite for data or send it changes |
| Outbound | Webhooks — a signed, verified message, e.g. sent when a record is updated | Push a real-time alert to any web address the moment a record changes |
| Inbound | Pull Connectors — SmartLite checks another system on a regular schedule | Fetch records from another system automatically and add or update them in SmartLite |
| Inbound | Inbound Webhooks (verified messages) / Bulk & Excel import | Receive data pushed from elsewhere — like a new order from an online store — and create or update CRM records automatically |
Same rules as manual entry
Every record that arrives this way is treated exactly like one entered by hand. Workflows, audit logs (the permanent change history), plan limits, and outbound webhooks all still apply.Rate limits are real
A rate limit caps how many requests you can make per minute — think of it as a speed limit for API traffic. Each API key gets 60 requests per minute on the Starter plan, more on paid plans. Go over it, and you get an error code 429 back, with a Retry-After header telling you how long to wait.1 Push closed deals to a finance webhook
Create an API keyGo to Integrations → API Keys → New Key. Name it "Finance Sync," with scopes READ + WRITE. Copy the key shown — it's only shown once, so save it somewhere safe.
Register an outbound webhookGo to Integrations → Webhooks → New Endpoint. Enter the URL of your test receiver, and pick the event
record.updated (fires whenever a record changes).Trigger itUpdate a real Opportunity's stage to "Closed Won" and check that your receiver got the message.
Verify the signatureCheck the
X-SmartLite-Signature header — a code that proves the message really came from SmartLite. Recompute it using your endpoint secret to confirm it matches.Test the API keyFrom a terminal, run:
curl -H "Authorization: Bearer <key>" http://localhost:8080/api/v1/records/opportunity and confirm you get your records back.Day-to-day: admins and finance ops
Add a new outbound connection when a system needs to knowRegister another webhook whenever a new downstream system needs real-time updates.
Check the delivery log when something looks offOpen Integrations → Webhooks to see the delivery/error history for troubleshooting.
Day-to-day: developers wiring up a new tool
Request a scoped API keyAsk an admin for a key with only the permissions your integration actually needs — READ-only if you're not writing data back.
Handle rate limits gracefullyWatch for a 429 response and respect the Retry-After header instead of hammering the API.
What to try next
Look at the Zapier Integration trail — it uses this exact same API key and webhook system, pre-wired for no-code tools.Test what you learned
1. A record created through a bulk API import — does it trigger Workflow Rules the same way a manual create does?
Yes — it's treated exactly the same as a record entered by hand
No — imported records skip workflows to save time
2. What happens when an API key goes over its rate limit?
The request quietly succeeds but gets queued up
You get an error code 429 back, with a Retry-After header