Skip to content
For LLMsView as Markdown·

imgix ​

undefined

DetailValue
CategoryMedia
Base URLhttps://api.imgix.com/api/v1
AuthenticationBearer Token
Endpoints5
Connector keyimgix

Using imgix in a workflow ​

  1. Go to Connections and click New Connection.
  2. Pick imgix 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 Sources
GET Assets
GET Upload
GET Purge Cache
GET Bandwidth Reports

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

GET ​

Sources

DetailValue
Operation IDsources_0
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your imgix connection from the Connection dropdown.
  3. In the Operation dropdown, select sources_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 imgix API reference.

GET ​

Assets

DetailValue
Operation IDassets_1
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your imgix connection from the Connection dropdown.
  3. In the Operation dropdown, select assets_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 imgix API reference.

GET ​

Upload

DetailValue
Operation IDupload_2
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your imgix connection from the Connection dropdown.
  3. In the Operation dropdown, select upload_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 imgix API reference.

GET ​

Purge Cache

DetailValue
Operation IDpurge_cache_3
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your imgix connection from the Connection dropdown.
  3. In the Operation dropdown, select purge_cache_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 imgix API reference.

GET ​

Bandwidth Reports

DetailValue
Operation IDbandwidth_reports_4
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your imgix connection from the Connection dropdown.
  3. In the Operation dropdown, select bandwidth_reports_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 imgix API reference.