automation.engineer
All case studies

Mondofora / Project case study

2021Recorded work

Valid, missing or used.
Each offer code gets
a clear response.

Mondofora needed a clear customer response for every submitted offer code. The workflow checked whether a code was valid, missing or already used, then selected the corresponding email path.

Client
Mondofora
Contribution
First-person build narration and troubleshooting
Project status
Configured branches & handover work

Tools & working context

Project scope and implementation.

  • AppSumo
  • forms
  • Google Sheets
  • Mailchimp
  • Make
  • status tags

01 / Business context

The problem
to solve.

A redemption form needs to do more than find a matching row. A customer can paste a code with extra whitespace, submit an unknown code or try one that has already been used. Each case needs a deliberate response.

The recorded work separated those cases and connected the resulting state to Mailchimp messaging. Related versions introduced expiry-date handling and refinements to the form trigger.

Inside the workflow

A closer look
at the handoffs.

Start with the main path and its branches. Select a step for context, or switch to the technical map for implementation detail.

  • Normalize submitted code
    Trim surrounding whitespace before looking up the submitted offer code.
  • Code and redemption sheet
    Search the shared code list and inspect its redeemed state.
  • Look up Mailchimp contact
    Read existing tags; continue without tags when the contact lookup has no result.
  • Remove prior response tags
    Clear old status tags so a repeated attempt can trigger its message again.
  • Valid and unused code
    A matching code without redeemed state follows the success path.
  • Previously redeemed code
    A matching record already marked redeemed follows the used-code path.
  • Code not found
    An empty code lookup selects the missing-code response.
  • Mark successful redemption
    Write redeemed state back to the code sheet on the valid path.
  • Apply used or missing-code tag
    Add or update the subscriber with the used-code or not-found response tag.
  • Apply successful-redemption tag
    Add or update the subscriber with the success tag before marking the code redeemed.
Read the workflow notes
  1. 01 / Validate

    Normalize and look up the code

    Form input was trimmed and compared with the code records. Separate paths identified missing or previously used codes; another version considered expiration.

  2. 02 / Record

    Apply the appropriate state

    A successful redemption updated the corresponding state. Contact lookup/tag handling accounted for missing tags and reapplication of status tags.

  3. 03 / Respond

    Drive the customer email handoff

    Mailchimp tags selected the relevant message path. Connection replacement and client-facing setup instructions supported the handover.

Concurrency handling and final account handover remained follow-up work.

03 / Implementation detail

How it
was built.

The message depends on both the submitted code and the customer’s previous attempts. Removing and reapplying the response marker allowed another attempt to select its message again.

A later test on Noah’s account explored processing new responses as they arrived instead of checking the sheet repeatedly. Client installation and field remapping were still pending, and speed or cost improvements were not measured.

Resending to the same email address and an IFTTT connection were requested or proposed in related material; they were not established as completed features.

04 / Outcome & scope

Result
and scope.

The configured process distinguishes valid, already-used and missing codes, handles repeat contacts and selects the matching customer response.

No fraud-prevention guarantee, concurrency protection or independently measured customer-support reduction is claimed.