Guides

Build with the OnRamp API

Practical, copy-paste recipes for getting data in and out of OnRamp. Each one starts with what you'll get and works against a live account in minutes — no deep coding required.

Prefer to explore first? Download the Postman collection (every endpoint, pre-wired for your API key) or point your AI assistant at llms.txt.

Onboarding health dashboard

See completion %, overdue work, and at-risk accounts across every onboarding — in a spreadsheet or a Monday-morning email — without opening OnRamp.

Read the recipe →

At-risk onboarding radar (Slack digest)

One Slack message every morning listing the onboardings that are stalled or overdue — with links straight to the project — instead of finding out in the QBR.

Read the recipe →

Mirror OnRamp without polling (webhooks + delta sync)

Keep a live copy of your OnRamp projects and tasks in your own database with ~99% fewer API calls — webhooks tell you what changed, you fetch just that.

Read the recipe →

Customer mention & comment alerts in Slack

The moment a customer comments or @mentions your team in OnRamp, a Slack alert appears with the message, the task, and a link — no more found-it-Friday.

Read the recipe →

Completion-gated provisioning & data handoff

The moment a customer finishes the gating task — security review signed, kickoff form filled — your systems provision automatically and post the confirmation back into OnRamp.

Read the recipe →

Webhook payloads & delivery reference

Every event OnRamp can send you, the exact JSON it delivers, and the delivery guarantees (ordering, duplicates, retries) your receiver should be built around.

Read the recipe →

Zero-touch kickoff — create projects from your own systems

A signup, a signed contract, or a closed deal in your systems spawns a ready-to-run onboarding project in OnRamp — pre-filled, assigned, and deduplicated. Works for one project or a 50-site rollout.

Read the recipe →

Two-way conversation bridge (OnRamp ↔ Slack)

Customer comments land in a per-project Slack thread; your team replies in Slack and the reply appears back in OnRamp — one conversation, two windows.

Read the recipe →