OTHER

Classify emailed job photos and reply with an accept-or-reject decision

Watches a field-ops inbox for emails with attached job photos, uses an AI vision model to verify the work matches the job description in the message.

CategoryOther
Enginesim
Difficultybeginner
Triggerevent
Steps4
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew email with photo attachments in field-ops inboxGmailGmail
  • ActionExtract attachments and verify against job description with OpenAIOpenAI
  • LogicBranch on approve vs reject
  • OutputSend approval or itemized rework reply via GmailGmailGmail

What it does

Some crews still send completion proof by email. This workflow monitors a shared Gmail inbox, pulls photo attachments out of incoming messages, and asks an OpenAI vision model whether the images satisfy the job described in the email body. It then sends an automatic reply: an approval confirmation, or a rejection that names exactly what is missing (wrong angle, work incomplete, no before/after).

When to use it

Use it for subcontractor or third-party crews who report by email rather than through your dispatch app, when you need a fast, consistent accept/reject reply instead of a manager triaging the inbox by hand.

How it works

  1. 1A new email in the field-ops Gmail inbox triggers the run.
  2. 2Photo attachments are extracted and the job description is read from the email body.
  3. 3OpenAI vision compares the photos against the description and returns approve or reject with reasons.
  4. 4A logic branch routes on the decision.
  5. 5Gmail sends an approval reply, or a reply listing the specific rework needed.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GmailRead, draft, send, label.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.