Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Zeplin

Zeplin integration for Flows360 workflows.

CategoryOther
Authenticationcustom
Version0.1.0
Published scopes0 published scopes
Last updatedSeptember 24, 2026

Overview

Connect Zeplin with Flows360

Zeplin integration for Flows360 workflows.

Use the Zeplin connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 6 actions and 2 triggers.

Available actions

  • Create Note
  • Find Project
  • Find Screen
  • Update Project
  • Update Screen
  • Custom API Call

Available triggers

  • New Note
  • New Screen

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Zeplin
  • Package: @activepieces/piece-zeplin@0.1.0
  • Exact artifact digest: sha256:5a09750953d6f7e3f021c978564e390e82eee54d9fbda720e17ea43ad0ba2955
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create Note (createNote), Create a note on a screen in Zeplin Classification: read.
  • Find Project (findProject), Find a project by name or retrieve all projects Classification: read.
  • Find Screen (findScreen), Find a screen by name or retrieve all screens in a project Classification: read.
  • Update Project (updateProject), Update a project's name and description Classification: read.
  • Update Screen (updateScreen), Update a screen's description Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Note, webhook.
  • New Screen, webhook.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects8
Supported actions6
Triggers2

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Zeplin Personal Access Token Required · protected credential

Supported objects

ObjectReadWriteNotes
Create Note Yes No Create a note on a screen in Zeplin
Find Project Yes No Find a project by name or retrieve all projects
Find Screen Yes No Find a screen by name or retrieve all screens in a project
Update Project Yes No Update a project's name and description
Update Screen Yes No Update a screen's description
Custom API Call Yes No Make a custom API call to a specific endpoint
New Note Yes No webhook trigger declared by the pinned package.
New Screen Yes No webhook trigger declared by the pinned package.

Supported actions

Create Note · Read

Create a note on a screen in Zeplin

create_note · Risk: low · Retry: safe

Inputs

  • projectId · string · Required, Select the Zeplin project
  • screenId · string · Required, Select the Zeplin screen
  • content · string · Required, The content of the note
  • color · string · Required, The color of the note
  • x · number · Required, The x coordinate position of the note on the screen
  • y · number · Required, The y coordinate position of the note on the screen
  • x_start · number · Optional, The starting x coordinate for range selection (optional)
  • y_start · number · Optional, The starting y coordinate for range selection (optional)
Find Project · Read

Find a project by name or retrieve all projects

find_project · Risk: low · Retry: safe

Inputs

  • projectName · string · Optional, Optional project name to search for (partial match)
Find Screen · Read

Find a screen by name or retrieve all screens in a project

find_screen · Risk: low · Retry: safe

Inputs

  • projectId · string · Required, Select the Zeplin project
  • screenName · string · Optional, Optional screen name to search for (partial match)
Update Project · Read

Update a project's name and description

update_project · Risk: low · Retry: safe

Inputs

  • projectId · string · Required, Select the Zeplin project
  • name · string · Optional, The new name for the project
  • description · string · Optional, The new description for the project
Update Screen · Read

Update a screen's description

update_screen · Risk: low · Retry: safe

Inputs

  • projectId · string · Required, Select the Zeplin project
  • screenId · string · Required, Select the Zeplin screen
  • description · string · Required, The new description for the screen
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Triggers

New Note · Webhook

Triggered when a new note is created on a screen

New Screen · Webhook

Triggered when a new screen is created in a project

Setup

Setup

  1. Add the Zeplin connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-zeplin@0.1.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 6 actions and 2 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Zeplin connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-zeplin@0.1.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com