Your website collects interest through Typeform: tour requests, membership inquiries, event RSVPs, but that interest doesn't do much sitting in Typeform's results tab. Someone has to notice each submission and manually add it to Flex before your team can follow up. Connecting Typeform and Flex through Zapier creates the right kind of record the moment someone submits, a sales lead for some forms, a simple contact for others.
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. Flex's Zapier actions only create new records; they can't update existing ones.
Prerequisites
Before you connect Typeform and Flex, confirm the following:
An active Typeform account, with each form below already built: Book a Tour, Membership Interest, and Event RSVP.
Admin access in Flex, using your Flex admin credentials or a Client ID and Client Secret if your organization uses SSO.
Important: Custom properties of type date or multi-select aren't supported in Flex actions, so if you're mapping a custom Typeform question into a Flex custom field, confirm the field type on the Flex side first.
Example workflows
Create a lead when someone books a tour through your website form
When someone submits your Book a Tour Typeform, this Zap creates the opportunity in Flex, along with the member behind it, so the lead is tracked the moment they show interest.
Trigger | Action |
 New Entry Triggers when a form is submitted.
Scope to your 'Book a Tour' form. |  Create Opportunity Creates an opportunity for a new member. This action also allows creating a new company. Also creates the member and, if provided, the company. |
Create a lead and opportunity with their preferred plan from a membership-interest form
When someone fills in your membership-interest form, this Zap creates the lead in Flex and notes which plan they're interested in, so sales can follow up with the right offer instead of a generic one.
Trigger | Action |
New Entry Triggers when a form is submitted.
Scope to your 'Membership Interest' form. | Create Opportunity Creates an opportunity for a new member. This action also allows creating a new company. Map the member's plan answer into the 'Opportunity Name' field (for example, "Dedicated Desk inquiry, Jane Doe"). |
Important: There's no dedicated plan field on Create Opportunity, so the plan they want is captured as text in the Opportunity Name, not linked to an actual membership plan record in Flex. It won't pull in pricing or plan details anywhere else.
Capture event RSVPs as contacts for community follow-up
When someone submits your event RSVP form, this Zap adds them as a member in Flex, tagged by the event, so your community team has a list to follow up with, without treating every RSVP as a sales lead.
Trigger | Action |
New Entry Triggers when a form is submitted.
Scope to your 'Event RSVP' form. |  Create Member Creates a new member.
Use the 'Tags' field to mark the member with the event name (for example, "RSVP: April Mixer"). |
Note: This uses Create Member rather than Create Opportunity, since an RSVP isn't automatically a sales lead the way a tour or membership inquiry is. If you'd rather treat event attendees as leads to actively pursue, use Create Opportunity instead, as in the first two workflows.
FAQs
Can I use one Zap to handle all three forms?
No. Typeform's trigger watches one specific form at a time, so each of these needs its own Zap. A fourth form later means a fourth Zap.
Does this work for partial or abandoned form submissions?
Not by default. These workflows only fire on completed submissions. Capturing partial responses (someone who started but didn't finish) needs at least a Basic Typeform plan with "Send partial responses to integrations" turned on for that form, and a partial response will have fewer answers filled in, so mapping to a required Flex field could fail if that question wasn't reached yet.
Why doesn't the usual 15-minute delay apply here?
That delay only applies when Flex is the trigger. In all three workflows here, Typeform is the trigger, and Flex is the action, so the record is created as soon as Typeform's instant trigger fires.