Appearance
Zeplin
undefined
| Detail | Value |
|---|---|
| Category | Design |
| Base URL | https://api.zeplin.dev/v1 |
| Authentication | Bearer Token |
| Endpoints | 6 |
| Connector key | zeplin |
Using Zeplin in a workflow
- Go to Connections and click New Connection.
- Pick Zeplin 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 | List Projects |
GET | List Screens |
GET | List Components |
GET | List Styleguides |
GET | Get Screen |
GET | List Organizations |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET
List Projects
| Detail | Value |
|---|---|
| Operation ID | list_projects_0 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Zeplin connection from the Connection dropdown.
- In the Operation dropdown, select
list_projects_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 Zeplin API reference.
GET
List Screens
| Detail | Value |
|---|---|
| Operation ID | list_screens_1 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Zeplin connection from the Connection dropdown.
- In the Operation dropdown, select
list_screens_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 Zeplin API reference.
GET
List Components
| Detail | Value |
|---|---|
| Operation ID | list_components_2 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Zeplin connection from the Connection dropdown.
- In the Operation dropdown, select
list_components_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 Zeplin API reference.
GET
List Styleguides
| Detail | Value |
|---|---|
| Operation ID | list_styleguides_3 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Zeplin connection from the Connection dropdown.
- In the Operation dropdown, select
list_styleguides_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 Zeplin API reference.
GET
Get Screen
| Detail | Value |
|---|---|
| Operation ID | get_screen_4 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Zeplin connection from the Connection dropdown.
- In the Operation dropdown, select
get_screen_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 Zeplin API reference.
GET
List Organizations
| Detail | Value |
|---|---|
| Operation ID | list_organizations_5 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Zeplin connection from the Connection dropdown.
- In the Operation dropdown, select
list_organizations_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 Zeplin API reference.