Actions app
Creating and editing Actions
- Embedding an Actions app page in a website
- Viewing and managing Actions pages in the administrator
- Defining the Salutation to be used in the opening of letters to Targets for an Action
- Defining the letter content to be sent to the target and setting what elements are editable by the visitor
- Including the Supporter Address in the Closing of Letters to Targets
- Restricting Who Can Act by one or more municipalities
Creating and editing Custom Targets
Creating and editing Public Comment Targets
Linking to Actions on the front end of your site
Defining communication preferences & app defaults in the Configuration
- Viewing and editing app-wide Configuration settings for Actions
- Activate the Google Civic API for the Actions app
- Locating your AWS Host URL to enter into Actions Configuration
- Setting the FROM email address, FROM email name, and REPLY-TO email address for emails to targets
- What is KnowWho and Why Do I Need a KnowWho Customer Code?
- Enabling U.S. Senators as a Pre-Defined Targets
Managing Soapbox Actions data within Salesforce
Troubleshooting the Actions app
- Google Civic project retiring Representatives API in April 2025
- Why do visitors see "The provided API key has an IP address restriction...." error when submitting initial address form for an Action?
- Why do visitors see an "An action can only be supported once" error message after submitting an action?
- How can I notify the Google Civic API project of incorrect data for legislative or executive targets?
- Why is the information or headshot for my legislative or executive targets incorrect?
- Why do supporters receive the error "Client error: `GET http://clerk.house.gov/member_info/mem_contact_info.aspx?statdis=XXX` resulted in a `404 Not Found` response"?