Integrations & Orders Inbox

​

Overview

Bodha Route Planner connects to your existing business tools so orders flow directly into your Orders Inbox — geocoded, matched to customers, and ready to plan into routes. No manual re-entry, no copy-pasting, no spreadsheet juggling. Every integration follows the same pattern:

1. Connect a data source (CRM, spreadsheet, e-commerce store, or API)
2. Map your fields — tell Bodha Route Planner which fields correspond to address, customer name, order reference, etc.
3. Orders sync automatically on a schedule (or on demand)
4. Orders land in your Orders Inbox with status: ready or needs review
5. Select orders and plan them into routes
6. Delivery status writes back to the source system (where supported)

To manage integrations, go to Settings → Integrations or visit the Integrations page from the main navigation.

---

​

Live integrations

These integrations are available today.

---

​

Method CRM

Turn QuickBooks invoices into planned delivery routes. Every invoice you raise in Method CRM becomes an order in your Bodha Route Planner inbox — geocoded, matched to a customer, and ready to plan. When the driver delivers, the invoice updates itself, so nobody reconciles deliveries against paperwork by hand.

​

How to connect

1. In Method CRM, go to Integrations → API and generate an API key. The key does not expire.
2. In Bodha Route Planner, go to Integrations → Method CRM and click Connect.
3. Paste your Method API key. It’s encrypted on our side and never shown again — not even to you.
4. Map your fields — Bodha Route Planner reads one real invoice and shows you its actual fields with live values beside them. Map each field to the corresponding Bodha Route Planner field. Nothing is typed from memory — you see real data.
5. Set a start date and a filter for what counts as deliverable, so only relevant invoices arrive.
6. Click Save. Orders start syncing within 15 minutes.

​

Data mapping

​

Write-back

When a stop is completed or failed, the following data is written back to Method CRM:

• Delivery status (completed / failed)
• Date and time of delivery
• Tracking link
• Failure reason (if applicable)

Write-back goes into Method-only custom fields that you choose during setup. Your QuickBooks data is never modified — the integration refuses to write to any QuickBooks-owned field (balances, totals, dates, addresses), even if one is mapped by mistake.

​

Limits and notes

• Syncs every 15 minutes (Method CRM has no webhooks, so real-time sync isn’t possible). Press Sync now at any time for an immediate pull.
• One connection per organization. Multi-account support is not yet available.
• Works best if you raise the invoice before you deliver, not after.
• Old invoices are not imported — only records from your chosen start date forward.

---

​

Google Sheets

Rows in a shared Google Sheet become orders in your Bodha Route Planner inbox. This is the catch-all for work that arrives by phone, WhatsApp, or email and gets typed into a spreadsheet — it replaces the daily export-and-upload grind entirely.

​

How to connect

1. In Bodha Route Planner, go to Integrations → Google Sheets and click Connect.
2. You’ll see a service address (an email address). Copy it.
3. In Google Sheets, share your sheet with that service address. Viewer access is enough.
4. Back in Bodha Route Planner, paste the sheet URL and select the tab to sync.
5. Map your columns — tell the integration which column is the address, the date, the name, the phone number, etc.
6. Click Save. Click Sync now to pull in orders immediately.

​

Data mapping

​

Limits and notes

• Read-only — Bodha Route Planner never modifies your sheet.
• The entire sheet is re-read each sync. Very large sheets (thousands of rows) may take longer.
• Your team keeps editing the sheet as usual — Bodha Route Planner picks up new and changed rows on each sync.

---

​

REST API & Webhooks

For developers and technical teams: generate a scoped API key, call the REST API to read routes, create orders, and update stops — and register webhook endpoints to receive real-time callbacks when delivery events happen.

​

How to connect

1. Go to Integrations → API & Webhooks.
2. Click Create API Key.
3. Choose which scopes the key may access (e.g. routes:read, orders:write).
4. Copy the key — it’s shown only once.
5. Use the key as an X-API-Key header or Bearer token in your API calls.
6. Optionally, add a webhook endpoint — tell Bodha Route Planner where to POST when events happen.

​

What you can do

​

Webhook events

​

Webhook security

Each webhook endpoint has a signing secret. Bodha Route Planner sends an HMAC-SHA256 signature in the X-Bodha-Signature header. Verify it against the raw request body before processing — this ensures the webhook came from Bodha Route Planner, not a third party.

​

Limits and notes

• API keys are scoped — a key with routes:read cannot write orders. Create separate keys for separate systems.
• Rate-limited per key. Audit logs track every call.
• Multiple API keys supported — use different keys for different environments (dev, staging, production).

See the API Reference for full endpoint documentation, request/response examples, and error codes.

---

​

Coming soon

These integrations are planned but not yet built. Request one to move it up the build list — every request is counted against the account that made it, and that count is what decides the build order. You can request any of these from the Integrations page in your dashboard. In the meantime, export a spreadsheet from any of these systems and import it into your Orders inbox — the column mapping is remembered, so repeat imports take seconds.

---

​

The Orders Inbox

The Orders Inbox is your central queue for incoming work from all sources — integrations, API, manual entry, and spreadsheet imports.

​

Order statuses

​

Working with orders

1. View all orders — Filter by status, date, source, or search by reference / customer name.
2. Fix issues — Click orders in “Needs review” to correct the address or fill in missing fields. Bodha Route Planner re-geocodes automatically when you save.
3. Add to route — Select one or more orders and click Add to Route. Choose an existing route or create a new one.
4. Manual orders — Click Create Order to add one manually, or paste addresses to bulk-add.

​

Deduplication

Bodha Route Planner automatically detects duplicate orders based on the external reference ID. If the same order comes in from your integration twice, it updates the existing order instead of creating a duplicate. This is why setting an Order ID / Reference ID column is strongly recommended for all integrations.

---

​

Integration settings

For each connected integration, you can configure:

---

​

Troubleshooting