Send leads and proposals to Kelo
If your enquiries or proposals live somewhere other than Xero or QuickBooks — a web form, a CRM, a spreadsheet automation — you can push them into Kelo with a single request. Quiet ones then show up in your weekly number and Kelo drafts the chase. Nothing sends without your approval.
1. Get an API key
In Kelo, go to Settings → API keys and create a key. Copy it — it's shown once. Send it as a bearer token.
2. The fields Kelo needs
| Field | Required | Example | Notes |
|---|---|---|---|
contact_name | Yes | Apex Media | Who the proposal went to |
amount | Yes | 3000 | Proposal value in GBP (numbers only) |
sent_date | Yes | 2026-08-01 | When you sent it (YYYY-MM-DD or DD/MM/YYYY) |
contact_email | No | [email protected] | Matches your Xero contacts and lets Kelo chase |
proposal_number | No | Q-101 | Your own reference; also makes re-sends idempotent |
3. Send the request
POST to https://gokelo.com/api/ingest/proposal. Send one row, or many under rows. Re-sending the same row updates it rather than duplicating, so a re-run of your Zap is safe.
curl https://gokelo.com/api/ingest/proposal \
-H "Authorization: Bearer kelo_live_your_key" \
-H "Content-Type: application/json" \
-d '{
"contact_name": "Apex Media",
"amount": 3000,
"sent_date": "2026-08-01",
"contact_email": "[email protected]",
"proposal_number": "Q-101"
}'Using Zapier or Make
Add a Webhooks action (Zapier: “POST”; Make: “HTTP → Make a request”), set the URL above, add the Authorizationheader, and map your trigger's fields to the names in the table. Any tool that can send an HTTP request works the same way.
Kelo is operated by a sole trader registered in England.
Business address available on request. [email protected], replies within one working day.