Skip to content

Sync HTTP Configurations ​

TL;DR:

  • Create reusable request templates for synchronous API calls.
  • Define HTTP method, URL, headers, and expected response type.
  • Reference these configurations inside Actions nodes in your scenarios.

Overview ​

Sync HTTP Configurations are saved API templates that allow your bots to communicate with external web servers synchronously. Instead of writing request URLs, headers, and authentication keys repeatedly in multiple scenario nodes, you save them here once and select them as presets.

Location: Workspace Settings → Integrations → Sync HTTP

Configuration Options ​

When creating a configuration, you configure the core transport properties:

  • Configuration Name: An internal label.
  • Method: GET, POST, PUT, DELETE, PATCH.
  • URL: The destination API URL. You can use path parameters like https://api.example.com/v1/users/{user_id}.
  • Headers: HTTP headers (e.g., Authorization, Content-Type). Header values support global variables (e.g., {{global.API_KEY}}).
  • Expect Response: Tell the bot runtime whether to expect JSON or raw Text.
  • Success Statuses: HTTP status ranges (e.g., 200-299) that represent a successful execution.

Use the Test tab in the creation modal to run a dry-run request and verify your settings.

Node-Level Usage ​

After saving a preset, select it inside a scenario's Actions node:

  • Path parameters (like {user_id}) will be automatically detected and mapped to scenario variables.
  • Query parameters and Request Body are configured directly in the node.
  • Response Mapping allows you to extract fields from the API response and save them into user variables.

TeleGo.io Docs