Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Zendesk-sell

Sales CRM for pipeline management, lead tracking, and contact organization.

CategorySales And Crm
Authenticationcustom
Version0.2.0
Published scopes0 published scopes
Last updatedSeptember 24, 2026

Overview

Connect Zendesk-sell with Flows360

Sales CRM for pipeline management, lead tracking, and contact organization.

Use the Zendesk-sell 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 12 actions and 8 triggers.

Available actions

  • Create Contact
  • Create Lead
  • Create Deal
  • Update Contact
  • Update Deal
  • Create Note
  • Find Deal
  • Find Contact
  • Plus 4 additional declared actions.

Available triggers

  • New Contact
  • New Lead
  • New Deal
  • Updated Lead
  • Updated Contact
  • Updated Deal
  • Plus 2 additional declared triggers.

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: Zendesk-sell
  • Package: @activepieces/piece-zendesk-sell@0.2.0
  • Exact artifact digest: sha256:e575598192d765a9c171cb4182724db2f986935fe97840d5757681df4b47cc5d
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

CUSTOM AUTH. 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 Contact (create_contact), Create a new contact. Classification: read.
  • Create Lead (create_lead), Create a new lead record. Classification: read.
  • Create Deal (create_deal), Create a new deal under an existing contact. Classification: read.
  • Update Contact (update_contact), Update fields of an existing contact. Classification: read.
  • Update Deal (update_deal), Update fields of an existing deal. Classification: read.
  • Create Note (create_note), Add a note to a deal, lead, or contact. Classification: read.
  • Find Deal (find_deal), Look up a deal by ID or name. Classification: read.
  • Find Contact (find_contact), Find a contact by email, name, or other identifier. Classification: read.
  • Find Lead (find_lead), Find a lead by one or more fields. Classification: read.
  • Find Company (find_company), Finds a company (organization contact) by name, email, or phone. Classification: read.
  • Find User (find_user), Finds a user by ID, email, name, or status. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Contact, polling.
  • New Lead, polling.
  • New Deal, polling.
  • Updated Lead, polling.
  • Updated Contact, polling.
  • Updated Deal, polling.
  • Deal Enters New Stage, polling.
  • New Note, polling.

Verification

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

Capability summary

Authenticationcustom
Supported objects20
Supported actionsNot published
Triggers8

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Email Address Required
  • API Token Required · protected credential

Supported objects

ObjectReadWriteNotes
Create Contact Yes No Create a new contact.
Create Lead Yes No Create a new lead record.
Create Deal Yes No Create a new deal under an existing contact.
Update Contact Yes No Update fields of an existing contact.
Update Deal Yes No Update fields of an existing deal.
Create Note Yes No Add a note to a deal, lead, or contact.
Find Deal Yes No Look up a deal by ID or name.
Find Contact Yes No Find a contact by email, name, or other identifier.
Find Lead Yes No Find a lead by one or more fields.
Find Company Yes No Finds a company (organization contact) by name, email, or phone.
Find User Yes No Finds a user by ID, email, name, or status.
Custom API Call Yes No Make a custom API call to a specific endpoint
New Contact Yes No polling trigger declared by the pinned package.
New Lead Yes No polling trigger declared by the pinned package.
New Deal Yes No polling trigger declared by the pinned package.
Updated Lead Yes No polling trigger declared by the pinned package.
Updated Contact Yes No polling trigger declared by the pinned package.
Updated Deal Yes No polling trigger declared by the pinned package.
Deal Enters New Stage Yes No polling trigger declared by the pinned package.
New Note Yes No polling trigger declared by the pinned package.

Triggers

New Contact · Poll

Fires when a new contact is created in Zendesk Sell (polls for new records).

New Lead · Poll

Fires when a new lead is created (polls for new records).

New Deal · Poll

Fires when a new deal is created (polls for new records).

Updated Lead · Poll

Fires when an existing lead record is updated (polls for updates).

Updated Contact · Poll

Fires when an existing contact is updated (polls for updates).

Updated Deal · Poll

Fires when an existing deal is modified (polls for updates).

Deal Enters New Stage · Poll

Fires when a deal transitions into a specified pipeline stage by polling for updates.

Inputs

  • pipeline_id · string
  • stage_id · string
New Note · Poll

Fires when a new note is added to a record (lead, contact, deal) (polls for new records).

Setup

Setup

  1. Add the Zendesk-sell 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:
  • Email Address (email), required.
  • API Token (api_token), required; stored as a sensitive connection value.
  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-zendesk-sell@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 12 actions and 8 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 Zendesk-sell 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-zendesk-sell@0.2.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