Plentific
ERPConnect AI agents to Plentific, a property operations and maintenance platform. Agents raise work orders against a property, dispatch and track tasks, run inspections, and process contractor invoices.
What This Integration Enables
Plentific runs repairs and maintenance for UK housing providers and property managers, and the object that carries the business is the work order raised against a specific home. That is a different thing from a ticket. Behind it sits a tenant who is waiting, a contractor who has to be paid, a compliance obligation about response times, and a property that will still be there when the job is done. This connector gives agents the whole path. Create Work Order raises a job against a property and requires a category and a service UUID that belongs to that category, which is why the Categories and Services dictionaries exist and why a flow resolves them rather than guessing. Update Work Order changes title, priority, assignee, access notes and tags, and is also how a job is cancelled, by setting the status to Cancelled together with a closing reason. Add Work Order Note writes an internal note, Send Work Order Message reaches the appointed contractor from a named sender address, List Work Order Quotes returns what the contractors have priced, Approve Work Order Quote lets the job proceed to hiring, Create Recall Work Order raises a repeat visit that inherits the original property and category, and Get Work Order History returns the chronological record of how the job actually moved.
Around that sit the objects a maintenance operation cannot work without. Locations are the properties themselves, through List Locations, Get Location and Create Location. Tenants and owners are created and listed against those locations. Tasks carry the internal work that is not a contractor job, with List Tasks, Get Task, Create Task, Update Task and Add Task Comment. Invoices are read, approved and paid through List Invoices, Get Invoice, Approve Invoice and Pay Invoice, which means the money side of a repair closes in the same flow that opened it. Inspections are listed and created from a template against a location. Paging on the list operations uses limit and offset sent as pagination headers, and every list is filterable enough that a scheduled read can be scoped to one organisation, one property or one status.
This connector does have a trigger, and it is a real one. On Work Order Event registers a Plentific webhook subscription for a chosen work order event, covering created, updated, published, hired, completed, cancelled and more, and runs the flow on each matching delivery. One caveat belongs on the page rather than in a footnote. The subscription sets an endpoint secret, but Plentific's public specification does not document a delivery signature or verification mechanism, so deliveries are not signature verified. The right pattern is to treat the delivery as a notification rather than as evidence: let it wake the flow, then call Get Work Order and Get Work Order History and act on what the API says the record is. That costs one extra call and removes an entire class of failure where a flow acts on a payload it cannot authenticate.
Without FlowRunner
With FlowRunner
Use Case Scenarios
A quote that gets compared before it gets approved
A contractor submits a quote against an open repair. On Work Order Event wakes the flow. The agent re-reads the job with Get Work Order, pulls every submitted price with List Work Order Quotes, and reads Get Work Order History so it can tell a first attempt from a job that has already been out once. It then reads List Work Orders filtered to the same location so the approver can see what else has happened at that address this year. The whole package goes to the property manager in Microsoft Teams. Only after a person chooses does Approve Work Order Quote run, and Add Work Order Note writes the choice and its basis onto the work order so the reasoning survives the person.
A repair raised from the channel the tenant actually used
A tenant reports a fault through a contact centre, a portal or a messaging channel. The agent resolves the property with List Locations filtered on external reference so the record matches the housing provider's own asset register rather than an address string. It reads the Categories dictionary and then Services within the chosen category, because Create Work Order requires a service UUID that belongs to its category and a fault description long enough to be useful. The work order is raised with the tenant's access notes attached, and the reference is written back to the originating system in Zendesk. Where the fault description is too thin to categorise confidently, the agent asks the contact centre agent one clarifying question instead of picking a category and creating a job that gets bounced.
Invoices that close against the job they belong to
Contractor invoices arrive against completed work. On a schedule the agent calls List Invoices filtered to awaiting approval, and for each one calls Get Invoice for the amounts and line items and Get Work Order for the job it was raised against. It compares the invoiced amount to the quote that was approved on that job and to the closing state in Get Work Order History. Invoices that match the approved quote and a completed job are put forward with a one line summary. Anything that does not match, an invoice against a cancelled job, an amount above the approved quote, an invoice with no approved quote at all, is separated and named. Approve Invoice and Pay Invoice run only on what a person has signed off, and the reconciliation lands in Xero with the work order reference attached so the finance side and the operations side agree on what the repair cost.
Human-in-Loop Highlight
Approve Work Order Quote is the gate, because it is the moment a contractor is hired into somebody's home. The action's own description says what it does: it approves a contractor's quote on a work order, allowing the job to proceed to hiring. Everything upstream of that is reversible. A work order can be updated, retitled, reprioritised or cancelled with a closing reason. Once a quote is approved and the job proceeds, a contractor is scheduled, a tenant is told to expect them, and a price is committed against a property that a housing provider will be asked to justify. There is no unapprove. The second reason to gate it here is the one this connector is honest about: the trigger that surfaced the quote is not signature verified, so the payload that woke the flow is a notification and not proof. An agent that approves directly off a delivery is approving off an unauthenticated message. So the agent does the comparison work and stops. It posts to the property manager: "Work order WO-88214, no heating at 14 Ardleigh Court, has three quotes. Northgate Mechanical at 412 pounds, Halliwell at 388 pounds, and Croft Plumbing at 640 pounds. I re-read the job from the API rather than the webhook payload and the status is published, not hired. This property has had two heating jobs in the last five months, and the January job was closed by Croft. Halliwell is cheapest but has never worked this property. Approving a quote hires the contractor and I cannot take it back. Which one, or do you want a recall raised against the January job instead of a new hire?" The manager answers once. Approve Work Order Quote runs on that answer, and Add Work Order Note records the basis on the job. This is the human-in-the-loop moment on a platform where the agent can genuinely see more than a person can, every quote, every prior visit, every state change, and still has no standing to decide which contractor goes into a tenant's flat.
Agent Capabilities
28 actionsWork Orders
10- List Work Orders Returns maintenance work orders with filtering by status, location, organisation, external reference and the emergency and closed flags, sorted by creation date and paged with limit and offset.
- Get Work Order Returns a single work order by UUID with status, location, service, faults, contractor, tags and state history. This is the read that should follow every trigger delivery, because the delivery itself is not signature verified.
- Create Work Order Raises a maintenance job against a property. Requires an account code, a category UUID, a location, an organisation and at least one fault carrying a service UUID and a description. The service UUID must belong to the chosen category, so the Categories and Services dictionaries are resolved before the write.
- Update Work Order Changes title, priority, assignee, access notes, tags and external reference on an existing job, and cancels it by setting status to Cancelled together with a closing reason. Only the fields you provide are modified.
- Add Work Order Note Adds an internal note to a work order, optionally attaching previously uploaded files. This is where an agent records what it saw and what a person decided.
- Send Work Order Message Sends a message to the contractor appointed on a work order from a specified sender email, optionally using a message template. This reaches a real supplier, so it belongs downstream of a decision rather than inside a poll.
- List Work Order Quotes Returns every quote contractors have submitted against a work order, with amounts and quote status. This is the evidence read that runs before any approval is proposed.
- Approve Work Order Quote Approves a contractor's quote and allows the job to proceed to hiring. There is no counterpart that unapproves, which is why this runs behind a person.
- Create Recall Work Order Raises a recall against a completed work order when the original work has to be revisited, for a workmanship issue or an equipment failure. It inherits the original property and category, which is what makes repeat failures visible as repeats.
- Get Work Order History Returns the chronological status and activity history of a job, used to distinguish a first attempt from a job that has already been out and come back.
Properties
7- List Locations Returns properties with filtering by city, postal code and external reference, paged with limit and offset. Filtering on external reference is how a flow matches Plentific to a housing provider's own asset register.
- Get Location Returns a single property by UUID in full.
- Create Location Creates a property. Requires a location type UUID, an organisation and an address, and optionally sets a name, external reference, parent location, tags and access notes.
- List Tenants Returns tenants, optionally filtered by organisation.
- Create Tenant Creates a tenant linked to a property. Requires name, phone number, external reference, the location UUID and the organisation UUID.
- List Owners Returns property owners, optionally filtered by organisation.
- Create Owner Creates a property owner and links them to one or more locations.
Tasks
5- List Tasks Returns tasks with filtering by status and creation date range, paged with limit and offset.
- Get Task Returns a single task by UUID with status, assignee, due date and linked items.
- Create Task Creates a task, optionally with an assignee email, due date, priority, tags, and links to locations and work orders. This is how internal work that is not a contractor job stays attached to the property it concerns.
- Update Task Changes a task's title, assignee, due date, priority or status. Only the fields you provide are changed.
- Add Task Comment Adds a comment to a task, optionally recording the author email.
Invoices
4- List Invoices Returns invoices with filtering by status, organisation and work order, which is what allows a reconciliation flow to line an invoice up against the job it was raised for.
- Get Invoice Returns a single invoice by UUID with amounts, status and line items.
- Approve Invoice Approves an invoice that is awaiting approval.
- Pay Invoice Marks an invoice as paid, optionally specifying the payment method UUID to use.
Inspections
2- List Inspections Returns property inspections, optionally filtered by status and assignee.
- Create Inspection Creates a property inspection from a template against a location. Requires the organisation UUID, the template UUID and the location UUID.
Triggers
1 triggersEvent Triggers
1- On Work Order Event Fires when a work order changes on Plentific, covering created, updated, published, hired, completed, cancelled and more. It registers a Plentific webhook subscription for the chosen event and runs the flow on each matching delivery. The subscription sets an endpoint secret, but Plentific's public specification documents no delivery signature or verification mechanism, so deliveries are not signature verified. Treat the delivery as a notification that wakes the flow, then call Get Work Order and Get Work Order History and act on what the API returns rather than on the payload.
Frequently Asked Questions
What can FlowRunner do with Plentific?
FlowRunner agents can run List Work Orders, Get Work Order, and Create Work Order in Plentific, plus 25 more actions.
Does connecting Plentific to FlowRunner require OAuth?
Plentific uses a custom authentication method to connect to FlowRunner.
Can Plentific trigger a FlowRunner workflow automatically?
Yes. Plentific supports 1 trigger that can start a FlowRunner workflow automatically.
Start building with Plentific
$100 in credits. No card required. Connect in minutes.