Definition

The Typeform Submission Trigger starts a flow automatically when someone submits a form built in Typeform. Once connected, Zenphi listens for new responses on the selected Typeform and immediately triggers your automation flow upon each submission.

This trigger is ideal for automating follow-ups, storing submission data, sending notifications, or processing collected information. It's fully integrated with your Typeform account and provides access to both standard metadata (like submission time) and dynamic answers based on the actual structure of the form.

Key capabilities:

Instantly starts a flow when a Typeform is submitted
Access all submitted responses and metadata as outputs
Easily combine with Zenphi actions for emails, document generation, file updates, and more
Use Conditional Run to process only relevant submissions (e.g., based on answer values)

💡 Why Choose Typeform?

While Zenphi provides native support for Google Forms and even more powerful, tightly-integrated Zenphi Forms, there are specific use cases where Typeform can be a preferred choice — depending on your goals, audience, or brand experience.

Zenphi Forms are purpose-built for process automation: they offer more control, deeper integrations, and native compatibility with your Zenphi flows. So in most scenarios, Zenphi Forms will be the go-to option for smoother design-to-automation journeys.

However, Typeform stands out when:

User experience and brand presentation are key: Typeform is well known for its sleek, interactive, one-question-at-a-time interface, offering a highly polished and engaging experience.
You’re working on public-facing forms, customer satisfaction surveys, or brand-sensitive interactions where design matters just as much as functionality.
You already have existing Typeform forms and flows in use, and want to integrate them into your broader Zenphi automation strategy without rebuilding.

So while Zenphi Forms may offer the tightest integration, choosing Typeform as your input channel is still a smart option — and with Zenphi, you don’t have to choose just one. You can seamlessly automate across all of them.

Example Use Cases

1. Lead Capture to CRM

**Automatically log new leads into your CRM when a Typeform contact form is submitted.**Capture the user's name, email, and company from Typeform responses and create a contact record in HubSpot, Salesforce, or any other CRM tool supported by Zenphi.

2. Feedback Collection with Filtering (Conditional Run)

**Only process and route high-priority feedback for action.**Set a condition to run the flow only when the "Satisfaction Score" field is less than 3. Use Conditional Run to escalate such responses by creating a ticket or sending a Slack/Email alert to your support team.

3. Event Registration & Follow-Up

Handle event signups and automate post-submission communications. When someone registers via Typeform, use Zenphi to send a confirmation email, log them in a spreadsheet, and update your calendar or event system.

4. Internal Request Forms

Trigger internal workflows like access requests or equipment orders. Connect Typeform to Zenphi to automate approvals or request fulfillment based on form inputs. For example, if the "Urgency" field equals "High", send the request directly to a manager using Conditional Run.

5. Resume Intake and Categorization

Route incoming job applications based on department or role. Applicants select their preferred role in Typeform. Based on that choice (e.g., “Engineering”), Conditional Run directs resumes to the appropriate hiring team or Google Drive folder.

6. Client Onboarding with Custom Branching

Customize your onboarding flow based on client selections. Trigger different onboarding flows depending on a client’s selected package or service type in the Typeform. Conditional Run helps ensure only relevant steps and documents are generated.

7. Data Collection for Existing Systems

Push form data into third-party systems that don’t integrate directly with Typeform. Use Zenphi as the bridge — fetch the form values and send them via HTTP or API call to your internal systems using Zenphi’s HTTP or universal connector actions.

Configuration

Settings

1. Typeform Connection

This is your authenticated connection between Zenphi and your Typeform account. It enables Zenphi to access your forms and receive submission data securely. If you haven’t created a connection yet, you’ll be prompted to log into your Typeform account and authorize Zenphi to retrieve your form submissions.

2. Forms

Select one of the Typeform forms you have created previously in your Typeform account. This dropdown lists all forms accessible through the connected account. Choosing a form here means the trigger will listen for any new submissions to that specific form and start the flow when a submission occurs.

Tip: Make sure the form you select is actively collecting responses, as the trigger only fires when a new submission is recorded.

Conditional Run

The Conditional Run feature lets you control exactly when your flow starts after a Typeform submission. Even if a form is submitted, the flow will only run if the conditions you define are met. If not, the flow will be skipped, helping you avoid unnecessary processing.

This is especially helpful when you want the flow to trigger based on specific answers or criteria within the submitted form data — for example, only process submissions where the response to a question equals “Yes” or where a numeric answer exceeds a certain threshold.

🔁 How Conditional Run Works with Typeform Trigger

When enabled, you can build one or more conditions using AND / OR logic to finely tune when your flow activates. Each condition contains these parts:

Condition Type

When: The flow will run only if this condition is true.
Except When: The flow will skip if this condition is true.

Value to Evaluate

Choose which data to check. For the Typeform trigger, you can evaluate:

Trigger Outputs — like any of the form answers (the dynamic form controls), the form ID, form instance ID, or the submission timestamp.
Vaults — secure, static data such as API keys or tokens, managed under Settings → Vaults in your workspace.

🔐 Vaults Note: Vault values are secure and not visible or editable inside the flow. They can only be referenced during runtime.

Operator

Defines how you want to compare values. Options include:

Equals / Not Equals
Greater Than / Greater Than or Equal
Less Than / Less Than or Equal
Between
Is Null / Is Not Null

Comparison Value

The value you compare against, which can come from:

Trigger Outputs
Vaults
Or a manually entered fixed value (like a specific text or number)

🧠 Example Conditions for Typeform

Run the flow when the answer to a question “Are you interested?” equals “Yes”
Skip the flow except when a numeric rating score is greater than 3
Run the flow when the submission time is within business hours (e.g., between 9 AM and 5 PM)
Combine multiple conditions using AND/OR for advanced logic — for instance, only process submissions where a certain checkbox is checked and the email field is not empty

Outputs

When the Typeform Submission trigger activates, it provides a set of outputs containing the data submitted through the form, along with additional metadata about the submission. These outputs can be accessed throughout your flow using the token picker, and are also available for use in the Conditional Run section to control when your flow executes.

Here’s a breakdown of the key outputs:

1. Form Controls

These are the actual answers provided by the respondent to each question on your selected Typeform form. The outputs dynamically reflect the structure of your specific form, including text responses, multiple-choice answers, ratings, and more. This allows you to directly use the user’s input for further processing, such as sending emails, updating databases, or making decisions in your flow.

2. Form ID

This is the unique identifier of the Typeform form from which the submission originated. It helps you distinguish between different forms if you manage multiple Typeform forms within the same Zenphi workspace or flow.

3. Form Instance ID

Each submission has its own unique instance ID, representing that specific response. This is useful for tracking individual form entries or referencing them in follow-up actions or logs.

4. Created Time

This timestamp indicates exactly when the form submission occurred. It is especially useful for sorting, filtering, or applying time-based logic within your flow, such as triggering reminders or deadline notifications.

📄 Example Scenario: Filter Submissions Based on User Interest and Budget

Use Case:You're running a product inquiry form using Typeform for a premium service. The form includes:

A multiple-choice question: "Are you interested in our premium plan?" (Yes/No)
A number field: "What is your estimated budget?"

You only want the flow to run if:

The person answered "Yes" to being interested,
AND their budget is greater than 500.

How Conditional Run Helps:By enabling Conditional Run, you avoid wasting resources on submissions that are not relevant. Zenphi evaluates both responses automatically using the Typeform trigger outputs.

Setup Steps in Conditional Run:

Condition 1
- When
- Question: "Are you interested in our premium plan?"
- Operator: Equals
- Value: "Yes"
Condition 2
- When
- Question: "What is your estimated budget?"
- Operator: Greater Than
- Value: 500
Combine both using AND logic.

Result:Only qualified submissions — those who are interested and have enough budget — will initiate your Zenphi flow, such as assigning a sales agent or sending tailored product information.