Appearance
Giphy
undefined
| Detail | Value |
|---|---|
| Category | Media |
| Base URL | https://api.giphy.com/v1 |
| Authentication | API Key (Query) |
| Endpoints | 6 |
| Connector key | giphy |
Using Giphy in a workflow
- Go to Connections and click New Connection.
- Pick Giphy 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 | Search GIFs |
GET | Trending |
GET | Translate |
GET | Random |
GET | Stickers |
GET | By ID |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET
Search GIFs
| Detail | Value |
|---|---|
| Operation ID | search_gifs_0 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Giphy connection from the Connection dropdown.
- In the Operation dropdown, select
search_gifs_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 Giphy API reference.
GET
Trending
| Detail | Value |
|---|---|
| Operation ID | trending_1 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Giphy connection from the Connection dropdown.
- In the Operation dropdown, select
trending_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 Giphy API reference.
GET
Translate
| Detail | Value |
|---|---|
| Operation ID | translate_2 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Giphy connection from the Connection dropdown.
- In the Operation dropdown, select
translate_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 Giphy API reference.
GET
Random
| Detail | Value |
|---|---|
| Operation ID | random_3 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Giphy connection from the Connection dropdown.
- In the Operation dropdown, select
random_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 Giphy API reference.
GET
Stickers
| Detail | Value |
|---|---|
| Operation ID | stickers_4 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Giphy connection from the Connection dropdown.
- In the Operation dropdown, select
stickers_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 Giphy API reference.
GET
By ID
| Detail | Value |
|---|---|
| Operation ID | by_id_5 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Giphy connection from the Connection dropdown.
- In the Operation dropdown, select
by_id_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 Giphy API reference.