property management · maintenance communication

Work order confirmations

A Rentvine webhook fires on every new work order: the tenant gets a confirmation email through Gmail and the maintenance team gets the details in Slack.

client
Property manager and brokerage, San Diego
duration
1–2 weeks
built with
Zapier, Rentvine API, Gmail, Slack
trigger
Each new work order in Rentvine
One new work orderexample
  1. 1
    Work order createdRentvine webhook
    done
  2. 2
    Check the requesterTenant with an active lease only
    done
  3. 3
    Fetch property and tenantRentvine API
    done
  4. 4
    Render the emailRentvine template ID 26
    done
  5. 5
    Email the tenantGmail, HTML confirmation
    sent
  6. 6
    Alert the teamSlack #maintenance, with a link to the order
    sent
manual steps
0

left in confirming a work order

channels
2

per work order: tenant email and team Slack alert

slack alert
4

details posted: number, description, address, direct link

the challenge

Confirmations were sent by hand

Every new work order meant manually emailing the tenant and notifying the maintenance team. It took time and led to delays or missed messages, while keeping tenants informed and the team updated quickly was crucial for good service.

what I built

One webhook, two messages

  1. 01Filtered triggerA Rentvine webhook starts the Zap, which only continues for tenants with active leases.
  2. 02Tenant emailRentvine renders work order template ID 26 with property and tenant details, and Gmail sends it to the tenant.
  3. 03Team alertThe #maintenance Slack channel gets the work order number, description, property address and a direct link to it in Rentvine.
architecture

How it works

Rentvine webhook, Zapier filter and logic, Rentvine API lookups, then a Gmail email and a Slack alert.

  1. triggerRentvinenew work order
  2. automationZapierfilter & logic
  3. APIRentvine APIproperty & tenant
  4. emailGmailtenant notification
  5. team alertSlack#maintenance
under the hood

Technical highlights

Webhook and data processing

  • Trigger filtering: only work orders with a Lease ID and a tenant Requester Contact ID are processed.
  • Rentvine data retrieval: API calls fetch the full property and primary tenant information.
  • Email template rendering: the Rentvine API generates the HTML body and subject from template ID 26.

Notifications

  • Tenant email: a formatted HTML email goes out through Gmail with the subject and body from Rentvine.
  • Slack notification: an instant message to #maintenance with key details and a direct link to the Rentvine work order.
  • Message formatting: an HTML template for the email and Slack mrkdwn for clear messages.
ZapierRentvine APIWebhooksGmailSlack
keep reading

More on work orders

Need work order notifications like this?

Rentvine, Gmail, Slack or other tools: tell me which messages your team still sends by hand and I'll reply within a business day.

more work

Related case studies

This site uses cookies for analytics. Necessary ones are always on. Read the privacy policy