Create Response

Go to Product

Creates a model response. Provide text or image inputs to generate text or JSON outputs. Have the model call your own custom code or use built-in tools like web search or file search to use your own data as input for the model's response.

Options

Body

The JSON request body. Pre-filled with an example which is derived from the schema.

Validate JSON
Checks “Body” against the JSON schema of the API. This happens on demand only, i.e. a failed check does not prevent the node from being executed — ultimately, the API itself decides what it accepts.
Body: Validation
Result of the last “Validate JSON” run, i.e. a confirmation or the list of schema violations. Not saved with the node settings.
Result Format

Specify how the response should be mapped to the table output. The following formats are available:

Structured Table: Returns a parsed table with data split into rows and columns.

  • Metadata:
  • Top Logprobs:
  • Temperature:
  • Top P:
  • User: This field is being replaced by safety_identifier and prompt_cache_key. Use prompt_cache_key instead to maintain caching optimizations. A stable identifier for your end-users. Used to boost cache hit rates by better bucketing similar requests and to help OpenAI detect and prevent abuse. Learn more.
  • Safety Identifier:
  • Prompt Cache Key:
  • Service Tier:
  • Prompt Cache Retention:
  • Previous Response Id:
  • Model:
  • Background:
  • Max Tool Calls:
  • Text:

    Configuration options for a text response from the model. Can be plain text or structured JSON data. Learn more:

    • Text inputs and outputs
    • Structured Outputs
  • Tools:

    An array of tools the model may call while generating a response. You can specify which tool to use by setting the tool_choice parameter.

    We support the following categories of tools:

    • Built-in tools: Tools that are provided by OpenAI that extend the model's capabilities, like web search or file search. Learn more about built-in tools.
    • MCP Tools: Integrations with third-party systems via custom MCP servers or predefined connectors such as Google Drive and SharePoint. Learn more about MCP Tools.
    • Function calls (custom tools): Functions that are defined by you, enabling the model to call your own code with strongly typed arguments and outputs. Learn more about function calling. You can also use custom tools to call your own code.
  • Tool Choice: How the model should select which tool (or tools) to use when generating a response. See the tools parameter to see how to specify which tools the model can call.
  • Prompt:
  • Truncation:
  • Id: Unique identifier for this Response.
  • Object: The object type of this resource - always set to response.
  • Status: The status of the response generation. One of completed, failed, in_progress, cancelled, queued, or incomplete.
  • Created At: Unix timestamp (in seconds) of when this Response was created.
  • Completed At:
  • Error:
  • Incomplete Details:
  • Output:

    An array of content items generated by the model.

    • The length and order of items in the output array is dependent on the model's response.
    • Rather than accessing the first item in the output array and assuming it's an assistant message with the content generated by the model, you might consider using the output_text property where supported in SDKs.
  • Reasoning:
  • Instructions:
  • Output Text:
  • Usage: Represents token usage details including input tokens, output tokens, a breakdown of output tokens, and the total tokens used.
  • Prompt Cache Options: The prompt-caching options that were applied to the response. Supported for gpt-5.6 and later models.
  • Moderation:
  • Parallel Tool Calls: Whether to allow the model to run tool calls in parallel.
  • Conversation:
  • Max Output Tokens:

Raw Response: Returns the raw response in a single row with the following columns:

  • body: Response body
  • status: HTTP status code

Input Ports

Icon
Configuration data.

Output Ports

Icon
Result of the request depending on the selected Result Format.
Icon
Configuration data (this is the same as the input port; it is provided as passthrough for sequentially chaining nodes to declutter your workflow connections).

Popular Predecessors

  • No recommendations found

Popular Successors

  • No recommendations found

Views

This node has no views

Workflows

  • No workflows found

Links

Developers

You want to see the source code for this node? Click the following button and we’ll use our super-powers to find it for you.