Overview
Multiple feeds let you send form data to different services from a single submission. You might send entry data to multiple mailing lists, create records in different CRMs based on user choices, or route payments to different processors based on the selected product or payment type.
Understanding how different add-ons handle multiple feeds helps you configure them correctly and avoid unexpected behavior.
When you configure multiple feeds for a form without using conditional logic, the behavior depends on the add-on type.
Add-ons that process all feeds
Most add-ons will process every feed you’ve configured. If you have three MailChimp feeds set up, all three will fire when the form is submitted.
Add-ons that process only one feed
Payment add-ons (Stripe, PayPal, Authorize.Net) can only process one feed per submission. If you configure multiple payment feeds without conditional logic, only the first feed will process. The “first” feed is determined by feed ID (whichever feed was created first).
This is why conditional logic is essential when working with multiple payment feeds. Without it, you can’t control which payment processor receives the transaction.
Feed order
Some add-ons support feed ordering, which lets you control the sequence in which feeds execute. However, for payment add-ons, ordering doesn’t change the fact that only one feed will process, it just determines which one.
User Registration Feed Limitations
The User Registration add-on has specific restrictions on feed configuration:
Update feeds
You can only configure one Update feed per form.
Create feeds
You can configure multiple Create feeds per form. Create feeds generate new user accounts when the form is submitted. Using conditional logic, you can create users with different roles and custom user fields based on form choices.
For example, you might use conditional logic to:
- Create a Subscriber account if the user selects a free membership.
- Create a Contributor account if the user selects a paid membership.
- Create different user types based on a registration type field.