Skip to content

HTTP Request Step

The HTTP Request step lets a Flow send information to an external web service and use the response in later steps.

What this is

Use this step when Studio should call a URL as part of a Flow. Common examples include notifying another system, looking up a record, or sending a completed result to a business tool.

For external service design, authentication details, or integration code, use the Developer Hub.

When to use it

Use HTTP Request when:

  • An external system already provides a URL your workspace is allowed to call.
  • The Flow needs to send or retrieve information during execution.
  • The response should guide a later Condition, Ask to LLM, or Final step.

Use a built-in tool or integration instead when one is available, because those usually require less setup and are easier for admins to maintain.

Before you start

Make sure:

  • You have the correct URL from the system owner.
  • You know which method the external system expects.
  • Required headers or credentials are approved by your admin.
  • You know what a successful response looks like.
  • You have a fallback path for errors or empty responses.

Configure the step

  1. Add an HTTP Request step to the Flow.
  2. Enter the URL.
  3. Choose the method shown by the external system owner.
  4. Add required headers or body fields using the product UI.
  5. Use template variables for values produced earlier in the Flow.
  6. Save the response in an output variable.
  7. Connect the next step.

Use outputs in later steps

After the request completes, use the saved output variable in a Condition, Ask to LLM, Extract Data, or Final step.

Test the step

Test with safe sample data before using production records. Confirm that:

  • The request succeeds.
  • The external system receives the expected information.
  • The response is usable by the next step.
  • Error responses lead to a clear fallback message or branch.

Troubleshooting

The request fails

Check the URL, method, required credentials, and whether the external system is available.

The response is empty or hard to use

Ask the system owner what response format to expect, then use a data or condition step to handle it clearly.

Sensitive data is being sent

Review the Flow with an admin before sharing or publishing it. Only send data that the external system is approved to receive.

Studio · Pulse — Cognipeer product documentation