Your team sends membership agreements and contracts through DocuSign, while Flex holds the records for members and companies once they're onboarded. Chasing a signature and then re-entering that person's details into Flex by hand means onboarding stalls on whoever remembers to do both steps. Connecting DocuSign and Flex through Zapier sends the agreement out and creates the matching Flex record the moment it's signed.
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 DocuSign and Flex, confirm the following:
An active DocuSign account, with a Permissions Profile that allows the actions you plan to use (sending envelopes, in particular).
Admin access in Flex, using your Flex admin credentials or a Client ID and Client Secret if your organization uses SSO.
Important:
DocuSign's connection to Zapier uses a refresh token that expires after 30 days of inactivity. If a DocuSign Zap sits idle for a while, check the connection before assuming a trigger or action is broken.
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
Send a Flex contract for signature through DocuSign
When a new contract is created in Flex, this Zap sends it out for signature through DocuSign right away, so nobody has to remember to trigger it manually.
Trigger | Action |
 New Contract Triggers when a new contract is added. Filter it by organization, location, and status. |  Send Envelope Using Template Sends an envelope signature request using a template. |
Create a Flex member when a DocuSign envelope is completed
When a membership agreement is fully signed in DocuSign, this Zap creates the member in Flex, so onboarding starts the moment the signature comes in, not whenever someone checks their inbox.
Trigger | Action |
 Envelope Status Updated Triggers when an envelope is sent, completed, signed, voided, or declined. When this step triggers, Zapier will temporarily store documents in your envelope for processing and replaying in later Zap steps and data associated with the selected envelope. Some data may be unavailable if you do not have full access to the envelope. Filter by status set to 'Completed'. |  Create Member Creates a new member. |
FAQs
Can this integration update a Flex record if something changes in DocuSign later?
No. Flex has no action to update an existing member, company, or contract record, only to create new ones. If a signed envelope is later voided or corrected, that change won't be reflected in the Flex record this Zap already created. That would need to be handled manually.
Why does the Zap take a few minutes to run?
Zaps are triggered from a Flex run with a delay because Zapier checks Flex for changes on a polling cycle rather than in real time. This cycle usually runs every 15 minutes, so allow for that delay before troubleshooting a Zap that appears not to have fired.