As usual, the data gets sent to the CRM to make sure they’re subscribed to the email list. If the email address already exists, it might update the other data like phone & address. If not, it adds all of the data as a new record. Perhaps it also adds them to a “Yard Sign” segment and sends a confirmation email. Nothing new and remarkable yet.
But the purpose of this form is to distribute yard signs, not email list signups. So, we need to initiate a process that helps the campaign get that specific task done as efficiently as possible. For a smaller campaign, maybe that means just putting all the data into a Google Sheet or an Airtable base, and sending someone an email or Slack notification.
For larger campaigns, the request might need to be confirmed and delegated to different organizers based on location. So, with a user input step in the workflow, the data can be properly routed into separate lists. Taking that a step further, we could even automate this step by writing a script that uses the Google Geocoding and Distance Matrix APIs to calculate the distance to each field office or local organizer in a state, and then assign the option with the shortest distance.
To create a dynamic map displaying all of the yard signs, we’d configure a step that sends all the data from completed workflows into a central database or spreadsheet connected to some mapping software’s API, so that the team can visualize the exactly where the yard signs have been distributed.
Finally, we could configure a step that waits for an incoming webhook, perhaps from Airtable— When the organizer marks the entry as “delivered,” that would trigger another email to let the supporter know they’ve received their yard sign. This task could also be competed in the website’s admin dashboard. Of course, that extra email provides a great opportunity to make another specific fundraising ask!