Skip to main content
Every Action is a digital organizing and advocacy platform designed for nonprofits and political campaigns. It provides tools for donor management, email marketing, advocacy campaigns, and constituent relationship management to help organizations engage supporters and drive social impact.

​
1. Add your Every Action access

  1. In the Destinations tab, click on the “Add destination” button located on the top right of your screen. Then, select the EveryAction option from the list of connectors.
  2. Click Next and you’ll be prompted to add your access. The following configurations are available:
    • Application name: The application name associated with the API key.
    • API Key: The API key used to authenticate against EveryAction’s API service.
    • Should apply tag: Whether to associate tags with newly created contacts or not.
    • Tag column name: If you chose to apply tags, inform the name of the column that holds tag information on the input table. The tag value should be a string corresponding to the EveryAction tag ID.
  3. Click Next.

​
2. Select your data to send

  1. The next step is letting us know which data you want to send to the database. Select the layer and then the desired table.
    Tip: The table can be found more easily by typing its name.
  2. Click Next.

​
3. Map your Every Action data to send

  1. Select the fields from your selected table that you want to send.
  2. For each field selected from the catalog, configure the mapping rules that describe how the incoming stream fields should be mapped to EveryAction fields:
    • Lakehouse Column: The search path to get the value on the incoming stream (e.g., $.last_name, $.email[*].value).
    • EveryAction Field: The destination field name on EveryAction’s API (e.g., LASTNAME, EMAIL). Please note that this is case sensitive.
    • Default: An optional default value to be used for the field if the mapped column is empty or cannot be found on the source data.
  3. Click Next.

​
4. Configure your Every Action data destination

  1. Describe your destination for easy identification within your organization. You can inform things like what data it sends, to which team it belongs, etc.
  2. To define your Trigger, consider how often you want data to be sent to this destination. This decision usually depends on how frequently you need the new table data updated (every day, once a week, only at specific times, etc.).
  3. Click Done.

​
Check your new destination!

  1. Once completed, you’ll receive confirmation that your new destination is set up!
  2. You can view your new destination on the Destinations page. Now, for you to be able to see it on your Every Action account, you have to wait for the pipeline to run. You can monitor it on the Destinations page to see its execution and completion. If needed, manually trigger the pipeline by clicking on the refresh icon. Once executed, your data should be seen on Every Action.
If you encounter any issues, reach out to us via Slack, and we’ll gladly assist you!