Back to leads

Integration guide

Use one ingestion key for your workflow and a separate read-only key for Muse. Keys belong to your signed-in account. Never place keys in URLs or prompts.

Make.com / Pabbly Connect

  1. Choose a trigger in your CRM, form, or spreadsheet.
  2. Add an HTTP request action with method POST and URL: your connector origin followed by /api/webhook.
  3. Set headers Authorization: Bearer YOUR_INGESTION_KEY and Content-Type: application/json.
  4. Map the fields below. Use a stable unique event_id for retries.
  5. Send synthetic data first, then verify it appears in your dashboard.
{
  "event_id": "sample-001",
  "name": "Sample Buyer",
  "email": "buyer@example.com",
  "inquiry": "Please send a quote for 20 units.",
  "source": "Make demo",
  "stage": "new",
  "score": 85,
  "created": "2026-10-08T10:00:00Z"
}

All fields except created are required. Score must be an integer from 0 to 100. The workflow supplies the score; this connector does not invent an intent assessment. Repeated event_id values in the same account are acknowledged without inserting another record. Payload limit: 16 KiB.

Muse connection

Connection type: Raw API. API URL: this site's origin followed by /api. OpenAPI: /openapi.json. Documentation: /docs. Authentication: API key sent in the Authorization bearer header. Use only the read key.

The API is publicly reachable at https://leads.dodigital.marketing/api. All lead data routes require a scoped key or authenticated account.

Queries and export

GET /api/leads returns matching records; GET /api/export returns CSV. Both accept min_score (0–100), since (ISO timestamp), and limit (1–1000, default 100). Results are newest first; exports contain up to the selected limit. Use a narrower time filter for larger collections.

Errors: 401 means missing or incorrect key, 400 means invalid input, 413 means oversized payload, and 503 means temporary storage failure. Retry 503 with backoff and the same event_id; do not retry invalid payloads unchanged.

Data and access

Each database query is scoped to the signed-in user or key owner. Keys are stored as SHA-256 hashes and displayed only at creation. Read keys cannot ingest, revoke keys, or delete records. Browser mutations require same-origin requests. Use Data controls to revoke connections and delete stored lead records. Revoking all keys also deletes stored leads. Queries and exports exclude records older than 30 days. No lead data is used for model training or advertising.

This first version has no scheduled notifications or direct CRM OAuth. Lead follow-up is a query of your pipeline stage and inquiry data, not an outbound message action. Public launch requires final policy alignment, abuse protection and load testing; no million-user capacity has been established.

Support: samar@bloggingstudio.in