Mailchimp Secure Custom Fields Integration with Bit Flows

Create a New Workflow in Bit Flows

Go to:

Bit Flows → Create Workflow → Add Trigger

Select:

Trigger App

Mailchimp

Trigger Event

Watch Subscribe

Description:

This trigger starts the workflow whenever the Watch Subscribe event occurs in Mailchimp.

Connect Your Mailchimp

Select the Mailchimp source you want to automate and complete the connection settings required for the chosen trigger event.

Configure:

• The available source or event settings
• The incoming data provided by the trigger
• Any required connection information

The available options and data depend on the selected platform and trigger event.

Add Secure Custom Fields as an Action

Click:

Add Action → Secure Custom Fields

Select an Action Event:

• Get Options Page Field Value When “Watch Subscribe” occurs in Mailchimp, use the submitted data to run “Get Options Page Field Value” in Secure Custom Fields.
• Get Post Custom Field Value When “Watch Subscribe” occurs in Mailchimp, use the submitted data to run “Get Post Custom Field Value” in Secure Custom Fields.
• Get User Custom Field Value When “Watch Subscribe” occurs in Mailchimp, use the submitted data to run “Get User Custom Field Value” in Secure Custom Fields.

Description:

This action sends data from Mailchimp to Secure Custom Fields and performs the selected supported operation automatically.

Map Mailchimp Data with Secure Custom Fields Inputs

Map the available data from Mailchimp to the compatible inputs provided by the selected Secure Custom Fields action.

The exact values and inputs depend on the selected trigger and action events, so only map data exposed by those events.

Test and Activate Workflow

Run the Watch Subscribe trigger and verify the selected Secure Custom Fields actions:

• Confirm that Get Options Page Field Value completes successfully and processes the mapped data in Secure Custom Fields.
• Confirm that Get Post Custom Field Value completes successfully and processes the mapped data in Secure Custom Fields.
• Confirm that Get User Custom Field Value completes successfully and processes the mapped data in Secure Custom Fields.

Then activate your workflow.