Skip to content
For LLMsView as Markdown·

Zeplin

undefined

DetailValue
CategoryDesign
Base URLhttps://api.zeplin.dev/v1
AuthenticationBearer Token
Endpoints6
Connector keyzeplin

Using Zeplin in a workflow

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

DetailValue
Operation IDlist_projects_0
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

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

GET

List Screens

DetailValue
Operation IDlist_screens_1
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

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

GET

List Components

DetailValue
Operation IDlist_components_2
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

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

GET

List Styleguides

DetailValue
Operation IDlist_styleguides_3
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

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

GET

Get Screen

DetailValue
Operation IDget_screen_4
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

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

GET

List Organizations

DetailValue
Operation IDlist_organizations_5
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

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