Appearance
Replicate
undefined
| Detail | Value |
|---|---|
| Category | AI |
| Base URL | https://api.replicate.com/v1 |
| Authentication | Bearer Token |
| Endpoints | 6 |
| Connector key | replicate |
Using Replicate in a workflow
- Go to Connections and click New Connection.
- Pick Replicate from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
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
| Detail | Value |
|---|---|
| Operation ID | predictions_0 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Replicate connection from the Connection dropdown.
- In the Operation dropdown, select
predictions_0. - 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
| Detail | Value |
|---|---|
| Operation ID | models_1 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Replicate connection from the Connection dropdown.
- In the Operation dropdown, select
models_1. - 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
| Detail | Value |
|---|---|
| Operation ID | versions_2 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Replicate connection from the Connection dropdown.
- In the Operation dropdown, select
versions_2. - 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
| Detail | Value |
|---|---|
| Operation ID | trainings_3 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Replicate connection from the Connection dropdown.
- In the Operation dropdown, select
trainings_3. - 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
| Detail | Value |
|---|---|
| Operation ID | collections_4 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Replicate connection from the Connection dropdown.
- In the Operation dropdown, select
collections_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
| Detail | Value |
|---|---|
| Operation ID | deployments_5 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Replicate connection from the Connection dropdown.
- In the Operation dropdown, select
deployments_5. - 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.