Dumpster Controls · agent page

This is the agent-optimized version of https://dumpstercontrols.io/help/api/integration-recipes: the same content as the human page, without scripts, styles, animations or navigation. People should open the full page.

Canonical page
https://dumpstercontrols.io/help/api/integration-recipes
Last updated
2026-08-22
Tokens
752 tokens (cl100k_base), within the 2,500-token budget for a help page
Size
7.0 KB for this page, against 22 KB for the human page (68% smaller)
Markdown
https://dumpstercontrols.io/help/api/integration-recipes.md, or send Accept: text/markdown to the canonical URL
Cite as
Integration recipes: GoHighLevel, Zapier, Make, Sheets. Dumpster Controls. https://dumpstercontrols.io/help/api/integration-recipes (accessed 2026-11-16).
More for agents
Facts sheet · llms.txt · llms-full.txt · All agent pages · Product manual

Developer API · updated 2026-08-22

Integration recipes: GoHighLevel, Zapier, Make, Sheets

Concrete patterns for the most requested integrations. Each recipe uses only what is documented in this manual, so it works today.

  1. ## GoHighLevel: funnel to lead
    In your GHL funnel or workflow, add a webhook action that POSTs the form fields to /v1/leads with your Authorization header (map name, phone, email, address). The prospect appears in Dumpster Controls under Customers, Leads, seconds after submitting. Reverse direction: point a Dumpster Controls webhook (order.created, payment.received) at a GHL inbound webhook trigger to advance the contact's pipeline stage automatically when they actually book or pay.
  2. ## Zapier or Make: no polling needed
    Create a "Webhooks by Zapier" (or Make custom webhook) trigger, paste its catch URL into Settings, API, Webhooks, and select events. Each event becomes a Zap run with the payload fields ready to map. For actions, use the HTTP request step with your dc_live_ key to POST leads or GET data.
  3. ## Google Sheets reporting
    A daily Apps Script (or a Zapier schedule) inside your window: GET /v1/orders?from=<first of month>&per_page=100, loop pages, write rows. Money fields are plain dollar numbers, so SUM() just works. Add /v1/junk-jobs for the full picture.
  4. ## Your own website form
    ```
    POST the form server-side to /v1/leads (never from the browser: the key is a secret). A thank-you page plus the lead.created webhook into your Slack or email keeps the whole loop tight.
    ```
  5. ## Payments and fraud stay on rails
    A deliberate design choice worth understanding: your integrations bring the DEMAND (leads, data flows), while payments keep running through Dumpster Controls itself, with its built-in card processing, risk screening and fraud protection. The API cannot move money, which means a leaked key cannot either. When your lead converts and books, the payment happens on the platform with every protection intact, and your integration hears about it through the payment.received webhook.

Related guides

© 2026 Dumpster Controls. All rights reserved. Made in the USA.