Ingest
Seven source types
Pull from file upload, URL import, a webhook receiver, HTTPS, S3, GCS and SFTP — one connector abstraction over all of them. Postgres, Sheets, Salesforce and HubSpot are on the roadmap.
⇌AdaptivMapr
Capability · Connectors
Scheduled ingest in, signed batches out.
Pull from file upload, URL, webhook, HTTPS, S3, GCS and SFTP on an hourly, daily or weekly schedule — secrets KEK-encrypted. Push committed batches through a durable queue with a DLQ and admin replay.
POST /v1/connectors
What you get
Built for regulated workloads
Mapping is only useful if data can flow in on a schedule and results can flow out reliably. Connectors ingest from file upload, URL import, a webhook receiver, HTTPS, S3, GCS and SFTP — with every source secret KEK-encrypted and syncs on an hourly, daily or weekly cadence. On the way out, committed batches are delivered through a durable queue with a dead-letter queue and admin replay, HMAC-signed, with deterministic idempotency keys so a receiver can safely dedupe retries.
Secrets
KEK-encrypted credentials
Connector secrets — bucket keys, SFTP passwords, tokens — are encrypted with a key-encryption-key, stored service-role-only. The cascade never needs them in the clear.
Schedule
Hourly, daily or weekly
Each connector runs on the cadence you set, driven by a Worker cron. A recurring source pairs naturally with layout reuse — the same header row re-maps with zero AI every run.
Deliver
Durable webhook out
Committed batches are pushed through a Cloudflare Queue with a dead-letter queue and admin replay — a delivery that keeps failing lands in the DLQ for inspection and re-drive, not silent loss.
Signed
HMAC-signed & idempotent
Every outbound delivery is HMAC-signed so a receiver can verify it, and carries a deterministic idempotency key — sha256(uploadId::batchIndex) — so retries are safe to dedupe and never double-apply.
Try it
A real call, end to end
Register a connector with its source, schedule and (encrypted) credentials, and AdaptivMapr syncs it on cadence — mapping each pull and delivering the committed batch to your webhook.
Good to know
- Connector secrets are KEK-encrypted and service-role-only — never exposed to the cascade or the dashboard plane.
- Idempotency keys are deterministic — sha256(uploadId::batchIndex) — so a receiver can dedupe retries safely.
- Postgres, Google Sheets, Salesforce and HubSpot connectors are on the roadmap, not yet in v1.
curl
curl https://api.adaptivmapr.com/v1/connectors \
-H "Authorization: Bearer $MAPR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"name": "nightly-labs",
"source": { "type": "sftp", "host": "sftp.lab.example",
"path": "/out/*.csv", "secret_ref": "sftp_labs" },
"template": "lab_results",
"schedule": "daily",
"deliver_to": "https://hooks.example.org/mapr"
}'response
{
"id": "conn_4a91…",
"schedule": "daily",
"next_sync": "2026-07-10T02:00:00Z",
"delivery": { "signed": true, "dlq": true }
}FAQ
Common questions
File upload, URL import, a webhook receiver, HTTPS, S3, GCS and SFTP — all behind one connector abstraction with KEK-encrypted secrets. Postgres, Google Sheets, Salesforce and HubSpot are on the roadmap but not in v1 yet.
Delivery runs through a durable Cloudflare Queue: a failing delivery is retried, and one that keeps failing lands in a dead-letter queue where an admin can inspect and replay it. Nothing is silently dropped.
Every delivery carries a deterministic idempotency key — sha256(uploadId::batchIndex) — and is HMAC-signed. Your receiver verifies the signature and dedupes on the key, so a retried batch is applied exactly once.
Encrypted with a key-encryption-key and held service-role-only, separate from the user-facing dashboard plane. The cascade never sees them in the clear; it only ever handles the data a sync pulls.
Ready when you are
Put connectors & webhooks in production — without shipping raw records.
Spin up a key in minutes. Top up a $10 prepaid wallet — every map is a few tokens.
$10 minimum to start · pay only for what you map · PHI under BAA coverage