ValueChat
AI skills

Make HTTP request

Call a configured external API through a shared, protected connection.

Before you start

Use a test channel or sample conversation first. Confirm the visible result in ValueChat before applying the setup to production traffic.

How it works

  1. 01

    Set up a connection

    Set up a connection. Create an HTTP API connection from the connections manager. Choose no authentication, Bearer token or an API key header. Tokens are encrypted and are not placed in the model prompt.

  2. 02

    Configure an action

    Configure an action. Add Make HTTP request, choose a public HTTPS endpoint on port 443 and a fixed GET, POST, PUT, PATCH or DELETE method, then choose the saved connection. Give the action a meaningful name and clear usage instructions.

  3. 03

    Describe inputs

    Describe inputs. The agent can supply string query values and a JSON object body; GET has no body. Explain the required fields, accepted values and when to ask the customer for missing information. Fixed paths are supported; URL path templates, files and custom ports are not.

  4. 04

    Example

    Example. For a lead lookup, configure GET https://api.example.com/leads and instruct the agent to pass the confirmed email in query.email. For a write, configure a separate action with the intended endpoint and method.

  5. 05

    Results

    Results. A successful call returns its HTTP status and a bounded response body. HTTP failures return a failure result; the agent must not claim success. Responses are untrusted external data and must not override agent instructions.

  6. 06

    Safety and retries

    Safety and retries. Private network destinations and redirects are blocked. Query/body credentials are not a supported authentication method. ValueChat sends a stable Idempotency-Key per operation but the external service must honor it; exactly-once delivery is not guaranteed. After a timeout or interrupted write, verify the external state before retrying.

  7. 07

    Testing

    Testing. Test Agent does not send external HTTP calls. Test the real integration in an isolated environment before enabling it for customers. A shared connection may be used by multiple permitted agents, with each action retaining its own endpoint and method.

What to verify

✓The expected channel, conversation, contact or execution is visible.

✓The assigned person or agent matches the routing rule.

✓No customer-facing message claims an action that failed.

✓Activity or execution history contains enough context to investigate.

Need help?

Collect the workspace, channel, conversation and execution identifiers, then contact support@valuechat.app. Never send API keys or passwords.