Your support team works out of Zendesk, while your operations team manages members and companies in Flex. When a new member's ticket comes in, a support agent has no way of knowing who they are unless someone has already added them to Zendesk by hand. Connecting the two through Zapier creates a matching ticket, user, or organization in Zendesk automatically as members and companies move through their lifecycle in Flex.
This connection runs through Flex's own app in Zapier's directory, built on Flex's Zapier API. Each Zap has exactly one trigger and one resulting action, so a single Zap only ever moves data one way, from the trigger app to the action app. To move data the other way, you need a second, separate Zap.
Prerequisites
Before you connect Zendesk and Flex, confirm the following:
A paid Zapier plan. Zendesk is a premium app on Zapier.
An admin account in Zendesk with API token access enabled, so you can generate a token for the connection.
Admin access in Flex, using your Flex admin credentials or a Client ID and Client Secret if your organization uses SSO.
Important: Flex triggers in Zapier check for changes on a polling cycle, typically every 15 minutes, not instantly. Custom properties of type date or multi-select aren't supported in Flex triggers or actions.
Example workflows
These four Zaps cover a member's support footprint from their first day to their last.
Create a Zendesk ticket when a new member joins
When someone becomes a member in Flex, this Zap creates an onboarding ticket in Zendesk, so your support team has a task queued up to reach out, instead of waiting for the member to run into a problem first.
Trigger | Action |
 New Member/Member Status Updated Triggers when a new member is added or when a member's status is changed. Filter by organization, location, and status. |  Create Ticket Create a new ticket. |
Add new Flex members as Zendesk users
When someone becomes a member in Flex, this Zap adds them as a user in Zendesk, so they're recognized the moment they submit their first ticket instead of showing up as an unknown requester.
Trigger | Action |
New Member/Member Status Updated Triggers when a new member is added or when a member's status is changed. |  Find or Create User Finds a user, or creates one if none are found. Match by email, so a member who contacted support before joining doesn't get duplicated. |
Add new Flex companies as Zendesk organizations
When a new company joins in Flex, this Zap creates a matching organization in Zendesk, so tickets from that company's members get grouped together and agents can see the full account.
Trigger | Action |
 New Company Triggers when a new company is added. Filter by organization, status, and location. |  Find or Create Organization Finds an organization, or creates one if none are found. |
Create a Zendesk ticket when a member cancels
When a member's status changes to canceled, this Zap creates an offboarding ticket in Zendesk, so your team works through a checklist (revoke access, final invoice, exit survey) instead of relying on memory.
Trigger | Action |
 New Member/Member Status Updated Triggers when a new member is added or when a member's status is changed. Filter by status. |  Create Ticket Create a new ticket. |
Note: This Zap uses the same Flex trigger as the onboarding ticket Zap above, filtered on a different status. Setting up both is fine. They run independently.