Skip to content
For LLMsView as Markdown·

Replicate

undefined

DetailValue
CategoryAI
Base URLhttps://api.replicate.com/v1
AuthenticationBearer Token
Endpoints6
Connector keyreplicate

Using Replicate in a workflow

  1. Go to Connections and click New Connection.
  2. Pick Replicate from the marketplace.
  3. Enter your credentials (see Authentication above for what's expected).
  4. In a workflow, drop an API Call node and select this connection.
  5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

EndpointSummary
GET Predictions
GET Models
GET Versions
GET Trainings
GET Collections
GET Deployments

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET

Predictions

DetailValue
Operation IDpredictions_0
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Replicate connection from the Connection dropdown.
  3. In the Operation dropdown, select predictions_0.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Replicate API reference.

GET

Models

DetailValue
Operation IDmodels_1
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Replicate connection from the Connection dropdown.
  3. In the Operation dropdown, select models_1.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Replicate API reference.

GET

Versions

DetailValue
Operation IDversions_2
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Replicate connection from the Connection dropdown.
  3. In the Operation dropdown, select versions_2.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Replicate API reference.

GET

Trainings

DetailValue
Operation IDtrainings_3
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Replicate connection from the Connection dropdown.
  3. In the Operation dropdown, select trainings_3.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Replicate API reference.

GET

Collections

DetailValue
Operation IDcollections_4
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Replicate connection from the Connection dropdown.
  3. In the Operation dropdown, select collections_4.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Replicate API reference.

GET

Deployments

DetailValue
Operation IDdeployments_5
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Replicate connection from the Connection dropdown.
  3. In the Operation dropdown, select deployments_5.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Replicate API reference.