Mythos

NOTE: 'Citizens' are members of our cooperative. Everyone in our databases is either a 'Citizen of One' or a 'Friend of Resonance'. Some automations are duplicated to speak to both audiences (i.e. ending the 'R$ Received' email to Citizens with "go give R$ to another Citizen" and ending the same email for Friends with "become a member by filling out this form".)

Wildest

My wildest desire is to create 📝Networked Structures for communication that enables us to create new rules/recipes for common exchanges within the community; a structure like:

  1. When a record is (a) created or (b) meets conditions, then do the following:
  2. Gather (a) record information and (b) information from its linked records.
  3. Customize email message with find and replace from template within linked record.
  4. Send email message to (a) one or (b) many people associated with (1) trigger record.

A simple example:

  1. Citizen is given R$ and creates a new record in LEDGER.
  2. 'R$ Received' email template is customized with data from record and linked records.
  3. The Receiving Citizen is emailed the customized template as a notification of this exchange.

A more complicated example:

  1. A Citizen submits a project update and creates a new record in UPDATES (coming soon).
  2. 'Project Update' email template is customized with data from record and linked records.
  3. Project co-creators are emailed the update and given encoded links as calls to action*.

*Encoded links act as a voting mechanism and enable a simple vote of those who receive the email.

Mildest

My mildest desire is to re-create our existing system for customizing templates (shown in the nuanced example below) with a find and replace mechanism for template emails in a table. This automation is what we use for email communication and one of our most used zap.

  1. {RM SEND} checkbox equals TRUE on a Citizen/Friend record
  2. Gather (a) record information and (b) information from its linked records.
  3. Customize email message with find and replace from template within linked record.
  4. Send email to Citizen/Friend from [email protected] email address.
  5. Mark {RM SEND} checkbox as FALSE.

NOTE: There are a few other things that happen in the existing version of this automation such as adding the record for that email to the {MESSAGES} field (emails sent to that individual).

Examples

Here's the simple example where the entire automation exists for a single notification email:

  1. Giving R$ to another Citizen shows a form built with 📝MiniExtensions (aka 📝Love Machine) which creates a new record in 📝One Ledger (LEDGER table of ONE ECO v5).
  2. 'OL // R$ RECEIVED // COO' Zapier automation triggered by 📝On2Air's "Record Updated" grabs the record information and information from linked records, compiles the email and sends it, and then updates the record to show that the process has been completed. See it.
  3. Here's the email received from [email protected] with the sender (me) in the signature.

Here's the more nuanced example where the automation send emails customized from a library:

  1. {LAST EMAIL} changed (manually or via automation) and {RM SEND} equals TRUE
  2. 'RESONANCE MACHINE (CAO) v3' Zapier automation triggered by webhook and encoded element found to be associated with email template (form pre-filled with recipient's info). Here's what the first part of the zapier automation looks like and the second.
    1. NOTE: In this example, the encoded field (a formula for a prefilled 📝MiniExtensions form for our wedding RSVP) had been deleted and was not added to the sent email.
  4. Here's the email received from [email protected] with the sender (me) in the signature.
    1. NOTE: Our 📝SendGrid is only setup to send from brian@ and citizens@.

Contexts

Created with 💜 by One Inc | Copyright 2026