gohighlevel

Agency: per-client billing via sub-keys

Set up one TexAu workspace per agency client. Issue scoped sub-keys so usage rolls up to each client's bill separately.

The goal

Bill each agency client for their own enrichment usage โ€” without spreadsheet math.

๐ŸŸก Standard~25 min to first valuepass-through to clientagency

What you provide.

  • Client list

The action chain.

Each step uses a real TexAu actionKey. Click the step to read the action's full reference.

  1. 1
    Syncgohighlevel-create-business

    Per-client GHL sub-account.

  2. 2
    Enrichfullenrich-work-email-enrichment

    Run enrichment scoped to the client's sub-key.

  3. 3
    Syncgohighlevel-create-contact

    Push contacts into the client sub-account.

What you get back.

  • Per-client enrichment usage report

Why this works.

Agency operators on Clay or Apollo can't bill clients separately โ€” usage rolls up to one account. TexAu sub-keys mean every API call is attributed to a client workspace, so monthly invoices write themselves. Pair with the GHL workspace-per-client model for end-to-end client isolation.

Deploy this workflow in your TexAu workspace.

Every workflow in the library is one click to deploy. Edit any step, swap providers, or fork it for a new ICP.

Ready to run it