Add Emails from Tally Form Submissions to Klaviyo Email List

When someone submits your Tally form, this trigger captures all form field responses including email addresses, names, and any custom fields you've added. You'll need to specify which Tally form should trigger this workflow.

What to configure: Select the specific Tally form by entering its form ID. You can find this in your Tally form's URL (e.g., tally.so/r/YOUR-FORM-ID) or in the form settings.

The workflow checks that the email field from your Tally form is not empty before attempting to add it to Klaviyo. This validation step stops the workflow early if someone submits the form without providing an email.

What to configure: Map the email field from your Tally form to the filter's input. The filter should check that this field "is not empty."

Common field names to look for: "Email", "Email Address", "Your Email", or whatever label you used in your Tally form.

The workflow retrieves all current profiles from your target Klaviyo list. This creates a reference dataset used in the next step to determine if the Tally form email already exists in Klaviyo.

What to configure: Select the specific Klaviyo list where you want Tally form submissions added. You'll choose from your existing Klaviyo lists by list ID or name.

To find your list ID: In Klaviyo, go to Audience → Lists & Segments, click your list, and find the ID in the URL (e.g., /list/ABC123).

The workflow loops through all profiles retrieved from your Klaviyo list and counts matches with the email from the Tally submission. The count will be either 0 (new email) or 1 (existing email), which determines the next steps.

What happens automatically: The workflow compares the Tally form email against every email in your Klaviyo list. The result is stored as a count that drives the branching logic.

If someone previously submitted a different form or made a purchase (creating a Klaviyo profile), but isn't yet on this specific list, this step adds them. This handles cases where profiles exist but aren't subscribed to every list.

What to configure: Specify the Klaviyo list ID (same list from Step 3) and map the profile ID from the matched profile to ensure the correct existing profile is added.

What happens automatically: The workflow uses the matched profile's ID to create the list relationship, skipping profile creation entirely.

If someone previously submitted a different form or made a purchase (creating a Klaviyo profile), but isn't yet on this specific list, this step adds them. This handles cases where profiles exist but aren't subscribed to every list.

What to configure: Specify the Klaviyo list ID (same list from Step 3) and map the profile ID from the matched profile to ensure the correct existing profile is added.

What happens automatically: The workflow uses the matched profile's ID to create the list relationship, skipping profile creation entirely.

Email count equals 0 (email is new to Klaviyo)

For completely new subscribers, the workflow creates a Klaviyo profile using data from the Tally form. You can map additional fields beyond email, such as first name, last name, phone number, or custom properties.

What to configure:

• Required: Email address from Tally form
• Optional: First name, last name, phone number, location, custom properties

Example field mapping:

• Email: {{tally.fields.email}}
• First Name: {{tally.fields.first_name}}
• Last Name: {{tally.fields.last_name}}

The workflow takes the newly created profile ID from Step 7 and adds it to the list you specified in Step 3. This ensures the new subscriber immediately appears in your Klaviyo list and receives any welcome flows or campaigns targeting that list.

What to configure: Specify the same Klaviyo list ID from Step 3 and map the newly created profile ID from Step 7 to create the list relationship.

What happens automatically: The profile becomes an active subscriber on the list and triggers any Klaviyo flows configured for new list members (like welcome series).