Add Customer Tags in Mantle from Tally Form Submissions

4 min setup

No coding required

Runs automatically

When someone fills out your Tally form, this workflow locates the corresponding customer record in Mantle and then creates a customer tag. Perfect for organizing leads from surveys, contact forms, or registration pages. Set up once and let new form responses become tagged customers in your system without manual data entry. Note that it is required for your Tally form to collect an email address, which will be used to locate the corresponding record in Mantle.

How it works

4 steps to start tagging customers in Mantle when they submit Tally forms

Form Submitted

App connector: [Tally](/content/apps/tally/integrate "View Tally integration page"/index.html)• Time to complete: 1 minute

Why this matters: This trigger captures form response data the moment someone submits your Tally form, providing the customer information needed to find and tag the right person in Mantle.

When someone completes and submits your Tally form, this step automatically captures all their responses including email address, answers, and submission timestamp. You'll need to connect your specific Tally form by selecting it from the dropdown menu in the trigger configuration. The form data gets passed to the next step to search for matching customers in your Mantle database. All form fields become available as variables for use in later workflow steps.

Get List of Customers

App connector: [Mantle](/content/apps/mantle/integrate "View Mantle integration page"/index.html)• Time to complete: 0 minutes (Auto-configured)

Why this matters: This step searches your Mantle customer database to find the person who submitted the form, ensuring you tag the correct customer account rather than creating duplicates or errors.

This step queries your Mantle customer database using the email address from the Tally form submission to locate the matching customer record. The search is configured to return only one customer result to keep the data clean and focused. You'll need to map the email field from your Tally form to the search query parameter. If a matching customer is found, their complete profile data gets passed to the filter step for validation before tagging.

Filter

App connector: [Filter](/content/apps/filter/integrate "View Filter integration page"/index.html)• Time to complete: 0 minutes (Auto-configured)

Why this matters: This validation step prevents the workflow from trying to tag customers who don't exist in your Mantle database, avoiding errors and ensuring the tagging action only runs when appropriate.

The filter checks whether the customer search returned a valid result by verifying the email field is not empty in the customer data. If no matching customer is found, the workflow stops here rather than attempting to add tags to a non-existent record. When a customer match is confirmed, the filter allows the workflow to proceed to the final tagging step. This prevents failed API calls and keeps your automation running smoothly.

Add Customer Tags

App connector: [Mantle](/content/apps/mantle/integrate "View Mantle integration page"/index.html)• Time to complete: 1 minute

Why this matters: This action applies the actual tags to the customer's Mantle profile, completing the automation by organizing your customers based on their form responses.

This step adds specified tags to the customer record that was found in the search step. You'll configure which tags to apply by entering them in the tags field - these can be static tags like "Newsletter Subscriber" or dynamic tags based on the form responses. The customer ID from the search step automatically populates the target for tagging. Tags help you segment customers for targeted marketing, personalized experiences, or customer service workflows.

Frequently asked questions

What happens if the same customer submits the form multiple times?

The workflow will find and tag the same customer record each time, so duplicate tags won't be created - Mantle typically prevents duplicate tags on the same customer. However, you might want to add a filter to check existing tags first if you need different behavior for repeat submissions.

Can I tag customers based on specific form answers rather than just submission?

Yes, you can customize the "Add Customer Tags" step to use dynamic tags based on form responses. For example, if someone selects "Enterprise" in a plan field, you could tag them with that specific value rather than a generic "Form Submitted" tag.

Will this work if the customer email in the form doesn't match exactly with Mantle?

No, the search requires an exact email match to find the customer record. If emails don't match due to different formatting, casing, or typos, the filter will stop the workflow. Consider adding a data transformation step to normalize email formats before the search.

Make this template your own!

Customize this workflow even further:

• Set conditional tags based on responses
• Apply different tags depending on form answers, such as tagging customers as "Premium Interest" if they select high-value options or "Support Priority" for urgent requests.
• Chain customer updates across platforms
• Extend the workflow to update customer records in multiple systems like email marketing tools, CRM platforms, or support systems when forms are submitted.
• Store form data in custom tables.
• Save detailed form responses in MESA tables for reporting and analysis, creating a comprehensive database of customer feedback and preferences.
• Deploy AI to analyze responses.
• Let AI agents evaluate form submissions and automatically assign priority levels, sentiment scores, or next-best-action recommendations based on customer responses.