OTHER

Maintenance Request Log and Vendor Routing in Airtable

Logs each photo-based maintenance request into Airtable, classifies severity from the image, and updates the record with the assigned vendor and SLA due date for tracking.

CategoryOther
Enginesim
Difficultyintermediate
Triggerwebhook
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerRequest submitted via webhookHTTP webhook
  • ActionLog raw request as new Airtable rowAirtableAirtable
  • ActionAnalyze photo for category and severityOpenAI
  • LogicAssign vendor and compute SLA due date
  • OutputUpdate Airtable record with vendor and SLAAirtableAirtable

What it does

Creates a single source of truth for facility requests in Airtable. Every submission is logged, its photo classified for severity, and the record enriched with the routed vendor and an SLA due date so nothing falls through the cracks.

When to use it

Use this when you need an auditable maintenance log, not just one-off dispatches. It is ideal for property managers tracking open issues, response times, and vendor accountability across many units.

How it works

  1. 1A webhook receives the request with photo, unit, and reporter details.
  2. 2A new row is created in the Airtable requests table with the raw submission.
  3. 3The photo is analyzed to determine problem category and severity.
  4. 4A logic step assigns the vendor for that trade and computes an SLA due date from the severity tier.
  5. 5The Airtable record is updated with severity, vendor, SLA due date, and a status of Dispatched, ready for tracking and reporting.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HTTP webhookTrigger any URL on agent actions.
  2. 2
    Connect AirtableBases, tables, views, automations.
  3. 3
    Connect OpenAIModels, embeddings, files.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    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.