Control Shift

‍

What can I do with the ControlShift Integration?

‍Ascend’s direct integration with Control Shift allows you to sync your Control Shift Petitions and set up custom sync logic between your Control Shift contacts and your Ascend Members. Synced petitions can be used in Integration automations to send confirmations, thank yous, and follow up texts.

How do I find members who have signed a ControlShift petition?

‍When a petition is synced, Ascend automatically creates a group with the same name as the petition. Any member who signs that petition is added to the group. To find these members, filter by the petition group in your Members list, Reports, or Inbox. To see a full changelog of when members were added, go to the Groups page, click the ellipsis (…) next to the group, and select Details.

How do I find all members sourced from ControlShift?

In the Members list, use the Source filter and search ControlShift. This will show all members who were added to Ascend through any synced petition.

What happens if I unsync a petition?

Ascend will stop receiving new signatures for that petition. The petition group and any existing member data will remain in Ascend. You must delete any associated automations before unsyncing a petition.

‍

Getting Started

Step 1: Connect Accounts

1. Login to your Control Shift account and keep your account open in a separate tab
2. From your Ascend account, go to Integrations and click Control Shift from the available Integrations
3. In the Connect Control Shift window Enter your organization’s unique ControlShift domain
   
   (example: https://ascend.controlshift.app/org)
4. Next create an API key in your Control shift account. Go to Settings > Integrations > API keys
5. Copy and paste the API key into the Ascend Connect Control Shift window
6. Copy the endpoint displayed in the Connect Control Shift window
7. From your Control Shift account go to Settings > Integrations > Webhooks and start a new webhook
   
   ‍DO NOT save the webhook until step 14
8. Paste the endpoint copied from Ascend for the webhook to point to 
9. Optionally create a Basic authentication user in Control Shift for your webhook
   
   Note: The username and password must match between your Control Shift and Ascend account
10. Under Advanced Settings in Control Shift, copy the sign in secret generated by Control Shift and paste it into the Connect Control Shift window in Ascend
11. If you created a basic auth user for the webhook, copy and paste the username and password into Ascend
12. Optionally, In the Connect Control Shift window toggle if you would like to Start syncing new Control Shift petitions right away
    
    Note: You can also turn this setting on after your integration has been configured. If you plan to sync custom fields with Ascend, we recommend that you do not turn this setting on at this step
13. Click Submit
14. Go back to your Control Shift account and save your webhook

‍

Step 2: Configure Field Sync Logic

1. Go to the Integrations page
2. Under your integrations, click the Control Shift Settings button
3. Go to the Fields tab to see all available core fields under the Default Field Mappings table, along with the Ascend Members list field they are mapped to
4. Update sync logic for a core field by clicking the Sync Behavior dropdown and selecting your desired sync logic
5. Sync additional fields, like custom fields, in the Additional Field Mappings table
   ‍

‍

Step 3: Configure Account Settings

1. Go to the Integrations page
2. Under your integrations, click the Control Shift Settings button, and click Settings in the top right corner
3. In the slide out pane toggle Sync Accounts to ON.
   
   Note: Once ON Ascend can send Control Shift payloads. If this setting is OFF Ascend will only process payloads received from Control Shift.
4. Optionally, select if you would like the integration to sync new members by toggling Import New Members to ON
   
   Note: If not enabled, Ascend will only sync with existing members in your Members list.
5. Optionally, select if you would like to sync new petitions automatically by toggling Sync New Petitions to ON
   
   Note: If not enabled, you will need to manually sync each new petition as they are created.

‍

Step 4: Sync Petitions

1. Go to the Integrations page
2. Under your integrations, click the Control Shift Settings button
3. Optionally, from the Petitions tab fetch any new petitions to sync by clicking Fetch New Petitions to fetch any new petitions on demand
   
   Note: Petitions are fetched several times a day automatically.
4. Select the petition(s) you would like to sync by clicking the Sync button in their corresponding row
5. Optionally, you can sync forms in bulk by selecting the forms you would like to sync, clicking Bulk Action > Sync Petitions

💡 Members who sign a synced petition are added to an auto-created group with the same name as the petition

‍

Members

When a supporter signs a synced petition, Ascend adds them to your members list.

• If a member with the same phone number already exists, Ascend updates their record, including a subscription status change.
• If no match is found, Ascend creates a new member record. They must be marked as subscribed in Control Shift.

To see which members came from ControlShift, filter by Source in the Members list.

‍

Groups

Autogenerated Groups

Ascend automatically creates a group for each synced petition, sharing the same name as the petition. Members who sign the petition are added to this group.

To see which members have signed your Control Shift petitions, filter for the petition group in the Members List, Reports, or Inbox.

To see a complete changelog of when members were added to your petition group, click the ellipsis (…) > Details from the Groups page.

‍

Automations

Synced petitions can trigger automations in Ascend. When setting up an automation, select the petition as the trigger (Signed, Signature Confirmed) and configure the member condition:

• New member — triggers only for supporters who are new to your Ascend list
• Existing member — triggers only for members already in your list
• Any member — triggers for all petition signers

Default Automation

You can set a default (fallback) automation that triggers for any synced ControlShift petition that does not have an explicit Integration automation.

To set up a default automation for your Control Shift integration, click Settings in the top right corner and configure your automation under Default Automation.