Pass-through integration for local government · records are never stored System status1-559-251-7767Sentra familySign in
SentraBridgeIntegration platform
Our productsConnector

Sentra Scheduler integration
for crews and field work

Sentra Scheduler plans field work: one-off visits, recurring jobs, crews and the customers they serve. Public works, parks and utility teams use it to schedule crews. It is made by the same company family as SentraBridge.

Pre-built connector

Sentra Scheduler

Tier
Pre-built connector
Category
Our products
Sign-in
API token (Bearer)
Paging
cursor
Webhooks
8 events, signatures verified
Sandbox
Yes: practice with made-up data
§ Overview

What connecting Sentra Scheduler does.

The pre-built connector reads, creates and updates visits, recurring jobs, customers and crews, and listens to signed webhooks for scheduled, changed and closed work. Flows link it with 311 and billing; visit details pass through without being stored.

  • Visits: Read changed visits; create and update status, customer, site, scheduled time and crew.
  • Recurring jobs: Read, create and update jobs: frequency, status, price per visit and crew.
  • Customers: Read, create and update customers and billing addresses.
  • Crews: Read, create and update crews.
What SentraBridge can do with Sentra Scheduler
resourcereadwritechanges onlyfields
Visitslist, read onecreate, updateyesID, Number, Status, Customer, Site, Scheduled for…
Recurring jobslist, read onecreate, updateyesID, Number, Title, Customer, Frequency, Status…
Customerslist, read onecreate, updateyesID, Name, Company, Email, Phone, Billing address…
Crewslistcreate, update—ID, Name

Webhook events: request.created request.scheduled request.status_changed request.closed customer.created customer.updated job.created job.updated

§ Use cases

What cities connect Sentra Scheduler for.

Potholes become crew visits

Every 15 minutes, new or changed pothole requests in Sentra 311 create a visit for the street repair crew.

Close 311 when the visit is done

The request.closed webhook updates the resident's 311 request when the crew finishes.

Recurring service to invoices

Completed visits on recurring jobs become QuickBooks invoices at the job's price per visit.

Customers from utility billing

New commercial accounts create Scheduler customers for scheduled service like grease trap checks.

§ Examples

Flows that use Sentra Scheduler.

Flow diagram: New pothole requests become Scheduler visitsEvery 15 minutes, takes new or changed pothole requests from Sentra 311 and creates a visit for the street repair crew in Sentra Scheduler.Every 15 minutesOn a scheduleChanged 311 requestsGet records · Sentra 311Open potholesFilterShape as a visitMap fieldsCreate Scheduler visitSend records · Sentra Scheduler
New pothole requests become Scheduler visits · 5 steps · a real SentraBridge template
§ How it works

How to connect Sentra Scheduler

  1. 01Get accessBuild and test flows on the Sentra Scheduler sandbox first.
  2. 02Add the connectionMachine tokens are coming to Scheduler; use the sandbox until they are.
  3. 03Preview real recordsThen add a Sentra Scheduler API token for SentraBridge.
  4. 04Turn it onFor webhooks, register the flow's address and signing secret.
§ Often connected with

Sentra Scheduler and the rest of city hall.

Systems cities commonly connect with Sentra Scheduler, each with its own connector page.

§ FAQ

Sentra Scheduler integration questions

How do 311 requests become Scheduler visits?

A flow reads new or changed requests of a type, like potholes, maps address and description, and creates a visit for the right crew. A template does this.

Does Sentra Scheduler send webhooks?

Yes, for requests created, scheduled, changed and closed, customers created and updated, and jobs created and updated.

Can visits be invoiced?

Yes. A flow can read completed visits and create invoices in QuickBooks Online or another billing system.

Connect Sentra Scheduler to the rest.

We'll set up a workspace with your systems in a sandbox and build your first flow with you.