Skip to main content

Integration steps

Integrations steps connect flows to external systems: HTTP Request for APIs and Google Sheets for spreadsheet logging.

Live URL: live.chatmaven.ai/workspaces/flows

HTTP Request​

Call an external HTTP API from a flow—for example to look up account data, validate an ID, or notify another system. Map parts of the JSON response into flow variables for use in later Message, Condition, or Update Contact steps.

Security
  • Store secrets in your API gateway or use server-side auth profiles configured in ChatMaven (Manage API connections).
  • Use HTTPS endpoints in production.
  • Restrict who can edit flows that contain HTTP steps in your workspace.

Configuration overview​

Add HTTP Request from STEPS under Integrations, then click the node to open the panel.

HTTP Request — connection and URL

FieldPurpose
ConnectionOptional auth profile (or None — no auth).
URLEndpoint. You may use {{variables}} in the URL where supported.
MethodHTTP verb (GET, POST, PUT, PATCH, DELETE).

HTTP Request — query parameters and headers

FieldPurpose
Query parametersKey/value pairs appended to the URL.
HeadersName/value pairs (for example Content-Type, Authorization).

HTTP Request — request body

FieldPurpose
BodyRequest payload for POST/PUT; JSON key-value, JSON raw, form URL-encoded, or raw text.

HTTP Request — response mapping and error handling

FieldPurpose
Response mappingMap JSON paths to variable names (for example $.data.balance → account_balance).
Save HTTP status as variableOptional status code variable (for example api_status).
On errorContinue on success path or follow failure branch.

Steps:

  1. Define the request (URL, method, headers, body).
  2. Add response mapping rows: JSON path → variable name.
  3. Wire OK and Fail ports on the canvas as needed.
  4. Save the step.
  5. Add a Condition step to branch on api_status or mapped fields when needed.

Typical pattern:

HTTP Request → Condition (status is 200) → Message (success)
                      └→ Otherwise → Message (error) or Assign To

Tips:

  • Map only the JSON fields you need; avoid storing full responses in variables.
  • Use test endpoints during development; switch to production URLs only when Active.
  • Whitelist ChatMaven egress IPs on your firewall if your API restricts by IP (ask support for current ranges).

Google Sheets​

Send flow data to Google Sheets when the integration is enabled.

  1. Connect Google Sheets under agent integrations first.
  2. Add Google Sheets from STEPS under Integrations.
  3. Click the node and Configure sheet — select target spreadsheet and sheet.
  4. Configure mapping — map columns from flow variables or contact fields.
  5. Save the step.

Tips:

  • Test with a single row before using in high-volume flows.
  • Place after data collection steps (Question, ChatMaven Form, HTTP Request) so variables are populated.

FAQ​

Can I use OAuth 2.0 login flows in HTTP Request?​

Use endpoints that accept static API keys or bearer tokens in headers unless your workspace documents a supported OAuth profile. Interactive OAuth consent flows are generally not suitable inside a single HTTP step.

What if the API is slow?​

Long requests may time out. Keep backends fast or use asynchronous patterns on your API where possible.

Why are my mapped variables empty?​

Check JSON paths, response content-type, and Flow validation notes. Empty variables may still render in messages using guest fallback text.