Action Network

ControlShift's Action Network integration allows organizations to have their ControlShift data automatically synced to their Action Network instance in realtime.

At ControlShift we're committed to making our tools work along with the other tools that your organization is already using, including CRMs. We don't want ControlShift-generated data to be excluded from your main systems, and we don't want organizers to waste their time shuffling CSVs between systems.

Action Network joins the list of CRMs that we integrate with to make it easy for you to run a distributed organizing program at scale.

Petitions

When users create and sign petitions, their contact information and details about the petition will be synced to Action Network. If the user already exists in Action Network, we'll update their member page appropriately. If the user does not already exist in Action Network, we'll create a new member page. 

The following user fields will be synced from ControlShift to Action Network:

• first_name
• last_name
• email
• postcode
• phone number (as a custom phone_number field in Action Network)
• custom signature fields (each as a custom field in Action Network, using the short_name used when adding the custom field to the ControlShift petition)

The petition that the user signed/created will be added to the user's Action History on Action Network. These Action History records will be tagged with Controlshift Petition  and the title of the petition. 

We'll also tag member records based on their role in ControlShift, either as controlshift-petition-signer or controlshift-petition-creator .

If the petition the user created/signed have tagged with ControlShift categories, we'll sync those categories to the user's Action Network record as user tags. These tags will take the form of controlshift:foo , where foo is the category name on ControlShift. 

Finally, if the petition is included in a partnership, the users' Action Network record will also be tagged with the partnership information. This tag will take the form of controlshift-partnership:bar where bar is the partnership's slug.

Events 

When users host and attend events, their contact information and details about the event will be synced to Action Network. If the user already exists in Action Network, we'll update their member page appropriately. If the user does not already exist in Action Network, we'll create a new member page. 

The following user fields will be synced from ControlShift to Action Network:

• first_name
• last_name
• email
• postcode
• phone number (as a custom phone_number field in Action Network)
• custom attendee fields (each as a custom field in Action Network, using the short_name used when adding the custom field to the ControlShift event)

The event that the user signed/created will be added to the user's Action History on Action Network. These Action History records will be tagged with Controlshift Event and the title of the event. 

If the ControlShift event is part of a calendar, we'll also add an Action History record related to the calendar itself. These records will be tagged with Controlshift Event Campaign and the title of the calendar.

We'll also tag member records based on their role in ControlShift, either as controlshift-event-attendee or controlshift-event-creator .

If the event is included in a partnership, the users' Action Network record will also be tagged with the partnership information. This tag will take the form of controlshift-partnership:foo where foo is the partnership's slug.

Subscriptions

Finally, we'll sync the user's ControlShift subscription status to Action Network.

• If the user is new to Action Network and subscribed to updates on ControlShift, we'll create a new member record and set them to subscribed in Action Network.
• If the user is new to Action Network and did not subscribe to updates on ControlShift, we'll create a new member record and set them to unsubscribed in Action Network.
• If the user already exists and is subscribed in Action Network, they'll remain subscribed in Action Network – regardless of whether they subscribe to updates on ControlShift.
• If the user already exists and is not subscribed in Action Network, we'll update them to subscribed if they subscribe to updates on ControlShift. (If they do not subscribe to updates on ControlShift they'll remain unsubscribed in Action Network.)

Users who unsubscribe from a single petition on ControlShift will not have their subscription status in Action Network changed. If the organization has global unsubscribes enabled, and the user chooses to unsubscribe from all organizational emails, that unsubscribe will be synced back to Action Network.

If you'd like to get started syncing information from ControlShift to Action Network, send us a support email.