Automate Hi Energy AI with n8n

Use n8n to schedule and orchestrate Hi Energy AI REST calls without custom servers. The built-in HTTP Request node authenticates with X-Api-Key, sends query filters, and returns JSON you can map into Google Sheets, Slack, Notion, databases, or downstream AI nodes.

Optimized for search and answer engines: HowTo steps, FAQ schema, credential guidance, and concrete HTTP Request examples for deals, advertisers, transactions, clicks, and contacts.

Authentication in n8n

Prefer the X-Api-Key header. In n8n, create a credential so the key is not stored as plain text inside the workflow canvas.

  1. Open Credentials → create Header Auth (or HTTP Header Auth).
  2. Name: X-Api-Key
  3. Value: your personal Hi Energy AI API key
  4. On the HTTP Request node, set Authentication to that credential
X-Api-Key: YOUR_API_KEY
Accept: application/json

Setup checklist

  1. Copy your API key from the API key page.
  2. Create an n8n Header Auth credential named X-Api-Key.
  3. Add a Manual Trigger or Schedule Trigger, then an HTTP Request node.
  4. Set Method GET and URL to https://app.hienergy.ai/api/v1/deals (or another resource below).
  5. Attach the credential, set Accept: application/json, and add query parameters.
  6. Execute the node, inspect JSON, then connect Sheets, Slack, or a database node.

HTTP Request examples

Configure each example as an n8n HTTP Request node. Replace query values as needed. Full field reference lives on each resource documentation page.

GET https://app.hienergy.ai/api/v1/deals?active=true&page=1&per_page=50

Flatten JSON:API deals.data[].attributes in a Set or Code node before writing rows.

Advertisers

Advertisers API docs

GET https://app.hienergy.ai/api/v1/advertisers?q=nike&page=1&per_page=25

Filter with network, country, status, or domain as supported by the Advertisers API.

Transactions

Transactions API docs

GET https://app.hienergy.ai/api/v1/transactions?start_date=2026-07-01&end_date=2026-07-27&status=approved

Use date windows that match your finance close; status may be pending, approved, paid, or corrected.

GET https://app.hienergy.ai/api/v1/clicks?start_date=2026-07-01&end_date=2026-07-27

start_date and end_date are required; the range cannot exceed 90 days.

GET https://app.hienergy.ai/api/v1/contacts?domain=example.com

Prefer domain or advertiser_name for useful results. Unverified contacts stay excluded unless allowed.

Pagination pattern

List endpoints typically accept page and per_page (or limit). In n8n:

  1. Start with page=1 and a stable per_page (for example 50).
  2. Use a Loop / Split In Batches pattern that increments page after each successful response.
  3. Stop when the returned collection is empty or shorter than per_page, or when next_page is missing.
  4. Respect rate limits on rate-limited endpoints: 1,000 requests/hour for non-exempt Hi Energy accounts and 10,000/hour for other non-exempt scopes; paid users and the extension account are exempt.
# Example query progression
?page=1&per_page=50
?page=2&per_page=50
?page=3&per_page=50

FAQ

Yes. Use the n8n HTTP Request node with your personal API key in the X-Api-Key header. The same REST endpoints documented for deals, advertisers, transactions, clicks, and contacts work in n8n workflows.

Create an HTTP Header Auth credential (or a generic Header Auth credential) with Name X-Api-Key and Value set to your Hi Energy AI API key. Attach that credential to the HTTP Request node instead of hard-coding the key in the workflow JSON.

Use the built-in HTTP Request node. Set Method to GET (or POST for create endpoints), URL to the full Hi Energy AI endpoint, Authentication to your Header Auth credential, and add query parameters as needed.

Most list endpoints support page and per_page (or limit). Loop with an n8n Loop Over Items or Split In Batches pattern, incrementing page until the response returns fewer items than per_page, or until next_page is absent.

The examples on this page are read-only GET imports. Creating contacts or other writes requires POST endpoints and the permissions documented on each resource API page.

Yes. This page publishes TechArticle, HowTo, FAQPage, BreadcrumbList, WebSite SearchAction, and ItemList structured data so assistants can cite a concrete n8n HTTP Request workflow.
Ask Dex AIIntegration help

If this page feels TLDR, ask Dex AI.

Dex AI speaks your language, and all the other languages you may not. It will write the integration for you with the right endpoint and headers in one plain-English answer.