| name | sales-ontraport |
| description | Ontraport platform help — all-in-one CRM + marketing automation + payments + dynamic CMS for small/mid-market businesses (ontraport.com): contacts, pipelines, email/SMS campaigns, automation, order forms/subscriptions, and membership pages on one database. Covers the object-based REST API (base api.ontraport.com/1, Api-Key + Api-Appid headers, every record is an object with an objectID, 180 requests/minute limit) and webhook subscriptions. Use when building an Ontraport API integration to sync contacts or transactions into a CRM or warehouse, figuring out the objectID model, hitting the 180-requests-per-minute rate limit, subscribing to a webhook for new-sale or tag events, the steep learning curve has you stuck, contact-overage charges are escalating your bill, the email editor is fighting you, or choosing a plan (Basic vs Plus vs Pro vs Enterprise). Do NOT use for choosing a CRM across vendors or comparing Ontraport vs Keap/HubSpot/GoHighLevel (use /sales-crm-selection). |
| argument-hint | [describe what you need help with in Ontraport] |
| license | MIT |
| version | 1.0.0 |
| tags | ["sales","crm","all-in-one","platform"] |
| github | https://github.com/Ontraport |
Ontraport Platform Help
Step 1 — Gather context
If references/learnings.md exists, read it first for accumulated platform knowledge.
-
What are you trying to do?
- A) Build a REST API integration — sync contacts/objects, read transactions, manage records
- B) Subscribe to a webhook — react to object created, form submitted, tag added/removed, product purchased, transaction added
- C) Configure a module inside Ontraport — CRM pipelines, Campaign Builder automation, email/SMS, order forms, dynamic CMS pages/membership
- D) Pick a plan — Basic vs Plus vs Pro vs Enterprise (note: per-contact pricing)
- E) Fix a problem — learning curve, cost/overage escalation, email editor, deliverability
- F) Something else — describe it
-
Where does data need to flow? Stay inside Ontraport / sync to a CRM or warehouse / drive an external app — this decides API vs webhook vs Zapier.
Skip-ahead rule: if the user's prompt already provides enough context, skip to Step 2.
Step 2 — Route or answer directly
| If the question is about... | Route to... |
|---|
| Choosing a CRM across vendors (Ontraport vs Keap vs HubSpot…) | /sales-crm-selection {question} |
| Email-marketing strategy and sequences | /sales-email-marketing {question} |
| Email deliverability / inbox placement | /sales-deliverability {question} |
| SMS marketing strategy / compliance | /sales-sms-marketing {question} |
| Membership-site / course structure and retention | /sales-membership {question} |
| Checkout / order-form / upsell conversion | /sales-checkout {question} |
| Affiliate / partner-program design across tools | /sales-affiliate-program {question} |
When routing, give the exact command, e.g. "This is a CRM-selection question — run: /sales-crm-selection {your question}".
Step 3 — Ontraport platform reference
Read references/platform-guide.md for the full reference — the module map (API/webhook/UI-only), per-contact pricing and plan limits, the object/contact/transaction data model with JSON shapes, and quick-start recipes (create a contact via the objects API; subscribe to a new-sale webhook; page through objects with range/start).
