Pexels

undefined

Detail	Value
Category	Media
Base URL	https://api.pexels.com
Authentication	API Key
Endpoints	5
Connector key	pexels

Using Pexels in a workflow

1. Go to Connections and click New Connection.
2. Pick Pexels 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

Endpoint	Summary
GET	Search Photos
GET	Curated
GET	Search Videos
GET	Popular Videos
GET	Collections

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

GET

Search Photos

Detail	Value
Operation ID	search_photos_0
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

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

GET

Curated

Detail	Value
Operation ID	curated_1
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

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

GET

Search Videos

Detail	Value
Operation ID	search_videos_2
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

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

GET

Popular Videos

Detail	Value
Operation ID	popular_videos_3
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

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

GET

Collections

Detail	Value
Operation ID	collections_4
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Pexels 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 Pexels API reference.