Allthings

Allthings is the tenant engagement and building operations platform for property managers. Agents work the property, unit, and tenant hierarchy, open and update service tickets, post articles and pinboard content, manage bookable assets and bookings, and export data on demand.

Verified 203 actions OAuth available

Allthings website Platform Documentation Capability data verified 2026-08-24

A signed tenancy arrives from the letting or property accounting system

Agent reads the unit reference, the tenant details and the start date

List Unit Utilisation Periods confirms the unit is genuinely vacant on that date

Create Utilisation Period opens the tenancy against the unit

Add File To Utilisation Period attaches the signed contract to the tenancy record

Agent posts the prepared registration invitation and the recipient to the property manager

The property manager confirms the recipient before Create Utilisation Period Invitation sends it

What This Integration Enables

Allthings is Swiss property technology: a resident app for buildings, and the operations layer the property manager runs it from. Anyone who reaches this connector expecting a task manager will be surprised by its shape. The unit of work here is not a task, it is the tenancy, which Allthings calls a utilisation period: a unit, a date range, and the people living in it. Tickets hang off a tenancy. Registration codes hang off a tenancy. A resident's access to their building's content ends when the tenancy's end date is set. Almost every useful workflow starts by resolving which tenancy a thing belongs to.

FlowRunner agents work that hierarchy from the outside in. They create properties, groups and units from the system that owns the portfolio, open and close tenancies as leases begin and end, raise and route service tickets, publish house notices and pinboard posts into the right channel, manage bookable assets such as a party room or a shared car, and pull CSV exports on a schedule. What makes this connector different from a work management connector is who is on the other end. Most writes here reach a private individual in their home, which is why the operations that send mail to residents are the ones FlowRunner puts a person in front of. Every action is built and verified against the Allthings API.

Without FlowRunner

Move-ins re-keyed twice The tenancy exists in the letting system and again in the resident app, entered separately by different people

Invitations sent in batches nobody counted A registration campaign goes out to a filter, and the recipient count is discovered afterwards

Tickets triaged by inbox order Requests arrive against a building rather than a tenancy, so routing to the right craftsperson is manual

With FlowRunner

The tenancy is written once The system that owns the lease creates the tenancy, attaches the contract and stops there

Sends reviewed with the count attached Any invitation reaching more than one household arrives as a proposal naming how many households it reaches

Tickets routed from the tenancy Each ticket carries its unit, its tenancy and the craftspeople assigned to that group before a human reads it

Use Case Scenarios

Move-in and move-out driven by the lease, not by a person remembering

A signed lease lands in the letting system. The agent resolves the unit through its external id, checks List Unit Utilisation Periods to confirm the unit is vacant on the start date, then calls Create Utilisation Period and Add User To Utilisation Period to open the tenancy and place the resident in it. Add File To Utilisation Period puts the signed contract and the handover protocol where the property manager will look for them. At the other end of the lease, Update Utilisation Period sets the end date, which is what actually stops the departing resident seeing the unit's content, and Soft Delete Utilisation Period frees the external identifier for the record that replaces it while keeping the history readable.
Service tickets that arrive already routed

A resident raises a request in the app, or one arrives by email and the agent creates it with Create Ticket For User against the resident's tenancy. The agent reads List Group Craftspeople and List Ticket Responsible Agents to work out who actually handles that kind of work in that building, sets the assignee and labels with Update Ticket, and posts a summary into Microsoft Teams for the facilities team. When a resident replies with a photo, List Ticket Files picks it up from the conversation and Download Ticket File puts it into FlowRunner file storage so it can travel to the contractor's system. Replies back to the resident go through Create Conversation Message, and the agent is explicit about whether a message is public or internal, because an internal note posted publicly is a note the resident reads.
Bookable assets, availability and the notice that follows

The building has a party room, a guest flat and two shared cars. The agent answers availability questions with Get Multiple Asset Availability in one call rather than one per asset, creates confirmed bookings with Create Booking, and uses Download Booking ICal to attach a calendar file to the confirmation. When maintenance is scheduled, Create Blocked Period closes the asset for the window, and because blocking does not cancel bookings already inside it, the agent reads List Asset Bookings first and posts the affected residents to the property manager. A notice goes out through Create Article into the right channel, and an SMS reminder to the affected households goes through Twilio.

Human-in-Loop Highlight

Bulk Invite is the operation on this connector that reaches the most strangers at once. It sends registration invitations to every code matching a set of criteria, and the criteria are a whole property or a whole app rather than a list of people, so the recipient count is a property of the filter and not of anything the caller typed. That mail reaches private residents in their homes and cannot be recalled. So the onboarding agent runs the filter, counts it with List Invitations, and stops: "The re-invitation filter for Bahnhofstrasse 12 matches 84 unused registration codes across 61 households, including 9 tenancies that ended in the last 30 days. Sending it mails all 84. Send, or should I exclude the ended tenancies first?" The property manager answers, the agent sends exactly the set that was approved, and nobody discovers the scope from the complaints. The agent counted. The person decided who gets mail.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

203 actions

Account and Access

Get Current User Returns the profile of the user the connection belongs to. Called first to discover the user id that every person-scoped operation needs.
Get My Minimal Data Returns a trimmed profile for the connection's own user. Cheaper when a flow only needs the id and the locale.
Get My Permissions Returns the permissions the connection holds, grouped by app. Read before a write so a flow learns it cannot make a change rather than discovering it as a rejection.
Get My Roles Returns the roles the connection holds, grouped by app.
List Channels Returns the channels the connection may use. A channel is Allthings' visibility path, and articles, community posts, tickets and file buckets are all scoped by one.

Apps

List Apps Returns the Allthings apps the connection can reach. An app sits at the top of the master data hierarchy.
Get App Returns one app by id.
Create App Creates a whole tenant engagement app in one call: the app, its property manager, its first admin user and their permissions, and optionally the master data structure. A provisioning operation rather than an everyday one.
Update App Changes an app's own settings, sending only the keys that should change.
Get App Configuration Returns an app's configuration: its enabled micro apps, its theming and its behavior settings.

Properties

List Properties Returns the properties the connection can see. A property is a site or an estate, holding the groups that hold the units.
List App Properties Returns the properties belonging to one app.
Get Property Returns one property by id.
Create Property Adds a property to an app. The external id is how a flow keeps an Allthings property tied to the record it came from in a portfolio system.
Update Property Changes a property. Setting an archived date here is the reversible way to retire one.
Delete Property Deletes a property along with the groups, units and tenancies beneath it. Archiving through the update operation is the alternative that keeps history.

Groups

List Groups Returns the groups the connection can see. A group sits between a property and its units, usually a building or an entrance.
List Property Groups Returns the groups belonging to one property.
Get Group Returns one group by id.
Create Group Adds a group to a property. The address here is the postal address residents see and the one an invitation letter is generated from.
Update Group Changes a group, sending only the keys that should change.
Delete Group Deletes a group along with the units and tenancies beneath it.
List Group Users Returns the people reachable through a group, gathered from its tenancies and from organizations attached to it. Broader than walking the tenancies yourself.
List Group Craftspeople Returns the craftspeople assigned to a group, which is who a ticket raised there can be dispatched to.

Units

List Units Returns the units the connection can see. A unit is a flat, an office or a parking space.
List Group Units Returns the units in one group.
Get Unit Returns one unit by id.
Create Unit Adds a unit to a group, which is how a portfolio change reaches the resident app.
Update Unit Changes a unit, sending only the keys that should change.
Delete Unit Deletes a unit along with the tenancies beneath it, and with them the tenancy history.
Check In To Unit Checks a user in to a unit using a registration code. The self service path a resident takes, as opposed to the administrative one.

Tenancies

List Utilisation Periods Returns the tenancies the connection can see. A tenancy is a unit plus a date range plus the people in it, and it is what tickets, registration codes and residents actually hang off.
List Unit Utilisation Periods Returns the tenancies of one unit, past and present. Including vacant periods is how a flow finds an empty unit.
List User Utilisation Periods Returns the tenancies one person belongs to. Results are narrowed by the caller's own permissions as well as by the user.
Get Utilisation Period Returns one tenancy by id.
List Utilisation Period Types Returns the tenancy types this account may use, which is what the type parameter on tenancy creation accepts.
Create Utilisation Period Starts a tenancy on a unit. Leaving the end date empty means open ended, which is the normal case for a running tenancy.
Update Utilisation Period Changes a tenancy. Setting the end date is how a move out is recorded, and it is what stops the residents seeing the unit's content.
Delete Utilisation Period Permanently deletes a tenancy. The soft delete is the alternative that keeps the record.
Soft Delete Utilisation Period Marks a tenancy deleted without removing it, clearing the external id so that identifier is free for a new record while the history stays readable.
List Utilisation Period Users Returns the people attached to one tenancy.
Add User To Utilisation Period Puts a person into a tenancy, either an existing user or a brand new one. Creating the user also sends an activation email, so a flow chooses that deliberately.
Remove User From Utilisation Period Takes a person out of a tenancy. The user account survives; what goes is their access to the unit's content.
List Utilisation Period Files Returns the documents attached to a tenancy, which is where a rental contract or a handover protocol lives.
Add File To Utilisation Period Attaches an already uploaded file to a tenancy. It takes a file id, which the upload operation produces.
Remove File From Utilisation Period Detaches a file from a tenancy.
Get Utilisation Period Consumption Returns the energy and water consumption recorded against a tenancy. Needs its own scope, separate from the tenancy scopes.

Users

List Users Returns the user accounts the connection can see.
Get User Returns one user account by id.
Create User Creates a user account. Allthings publishes no fixed field list here, so a flow supplies the body it needs, with email and locale as the usual minimum.
Update User Changes a user account, sending only the keys that should change.
Delete User Deletes a user account. Anonymizing keeps the record for statistics while stripping the personal data out, which is usually the right answer to a data subject request.
List User Addresses Returns the postal addresses a person is reachable at, derived from the tenancies they belong to.
Change User Password Sets a user's password, which requires the current one. The self service change rather than an administrative reset.
Send Password Reset Emails a password reset link to a user. The administrative path, and the one where no password passes through the flow.
Send User Invitation Emails an invitation to a user imported through the API. Allthings requires the person to be a property manager user with a company assigned.
List User Permissions Returns the permissions granted to a person.
List User Roles Returns the roles a person holds.
Assign User Permissions Grants a permission, or a batch of them, to a person. Each entry names a role and the object it applies to, so a permission is always scoped rather than global.
Delete Permission Revokes one granted permission by its own id.

Tenants

List Tenants Returns the residents of this account, with their registration and communication state.
Get Tenant Returns one tenant record by id.
Update Tenant Changes a tenant record. Allthings accepts only the username and the phone number here; everything else lives on the user account.
Get Tenant Stats Returns counts of tenants, invitations, communication methods and unregistered residents. A cheap health check for an onboarding flow.

Invitations

List Invitations Returns the unused registration codes with an email address. Used codes are not returned, so this is the read that counts an invitation campaign before it is sent.
Get Invitation Returns one registration code by id.
Create Invitations Creates registration codes and sends the invitations. Allthings publishes no fixed field list here, so a flow supplies recipients and tenants as the required pair.
Create Unit Invitation Creates an invitation on a unit's current tenancy. Used when a flow knows the unit but not which tenancy is running.
Create Utilisation Period Invitation Creates an invitation on a named tenancy. It can turn a duplicate into an add, putting the person into this tenancy rather than failing when an invitation for that address already exists.
Bulk Invite Sends invitations to every registration code matching a set of criteria, where the criteria are a whole property or app rather than a list of people. This is the operation the human gate on this page exists for.
Resend Invitation Sends the invitation email for one registration code again.
Update Registration Code Changes a registration code: its email, its language, the tenancies it grants and whether it is an instant invite.
Delete Invitation Deletes a registration code so it can no longer be redeemed.

Check In Requests

List Check In Requests Returns the check in requests waiting to be handled. A check in request is a resident asking to be let into a unit they claim to live in.
Create Check In Request Raises a check in request for the connection's own user against one or more groups.
Resolve Check In Request Accepts, rejects or archives a check in request. Accepting normally needs the tenancy the person is being let into.

Tickets

List Tickets Returns the service tickets the connection can see. This is the administrative view rather than one resident's.
Get Ticket Returns one ticket in full, including its conversations. It accepts either the internal id or the reference people see, so a flow can look one up from an email.
List User Tickets Returns the tickets one resident raised or can see.
Create Ticket Raises a service ticket against a tenancy. The description becomes the ticket's first comment, and an email notification goes to the address configured for the channel.
Create Ticket For User Raises a ticket on behalf of a named resident. The ticket still belongs to a tenancy rather than to the person.
Create Ticket For Property Manager Raises a ticket against a property manager rather than a tenancy, which is the route for work not tied to one flat.
Update Ticket Changes a ticket: its status, priority, assignees and labels. Suppressing the title change message keeps a bulk retitling out of every resident's message thread.
Delete Ticket Deletes a ticket and its conversation. Closing it through the update operation is almost always what a flow wants instead.
List Ticket Files Returns the files on a ticket, gathered from the conversation messages as well as the ticket itself, so a photo sent in a reply is included.
Download Ticket File Downloads one ticket attachment into FlowRunner file storage, so it can travel to a contractor's system.
List Ticket Responsible Agents Returns the people who handle tickets in the same channels as this one, which is who it can be assigned to.
List Ticket Custom Labels Returns the custom labels in use on tickets the connection can see, which is where label values should come from.

Conversations

List Entity Conversations Returns the conversations attached to a ticket, a booking or a user. A ticket's discussion lives here rather than on the ticket itself.
Create Entity Conversation Starts a conversation on a ticket, a booking, a user or a project.
Get Conversation Returns one conversation by id.
List Conversation Messages Returns the messages in a conversation.
Create Conversation Message Posts a message into a conversation. The message type decides who sees it: public reaches the resident and internal does not, so flows set it explicitly rather than by default.
Update Message Changes a message, for example to mark it read or to correct its content.
Delete Message Deletes a message from a conversation.

Assets

List Assets Returns the shared assets of one kind: bookable things such as a party room or a car, sharable ones, or salable ones. A date window narrows it to what is free.
Get Asset Returns one asset by id.
Create Asset Creates a shared asset. The time slot unit decides how bookings behave, because an hourly asset refuses a booking that does not land on a slot boundary.
Update Asset Changes an asset. Changing the time slot unit does not move bookings already made against the old one.
Delete Asset Deletes an asset along with the bookings against it.
Get Asset Availability Returns what is free on one asset across a date range.
Get Multiple Asset Availability Returns availability for several assets at once across one date range, which is what a booking picker actually needs.
List Bookable Asset Categories Returns the categories of bookable asset the connection's own tenancies give access to.

Bookings

List Asset Bookings Returns the bookings made against one asset. Read before blocking a window, because blocking does not cancel what is already booked inside it.
Create Booking Books an asset for a window. On an asset with hourly or quarter-hour slots, the window must land exactly on a slot boundary.
Get Booking Returns one booking by id.
Update Booking Changes a booking's window or its details, under the same slot boundary rule.
Delete Booking Cancels a booking.
List User Bookings Returns the bookings one person has made.
Download Booking ICal Downloads a booking as an iCal file into FlowRunner file storage, so it can be attached to a confirmation email.
Get Booking Stats Returns booking counts across the bookable assets the connection can reach. The read behind a utilization report.
List Blocked Periods Returns the windows an asset is deliberately unavailable, for maintenance or a private event.
Create Blocked Period Blocks an asset for a window so nobody can book it. Existing bookings inside the window are not canceled.
Update Blocked Period Changes a blocked window on an asset.
Delete Blocked Period Removes a blocked window so the asset can be booked in it again.

Articles

List Articles Returns the knowledge base articles the connection can see. Articles are per locale, so an article and its translations are separate records.
List My Articles Returns the articles visible to the connection's own user, already narrowed by their permissions and channels. The resident's view of the knowledge base.
List Article Categories Returns the article categories the connection's own user can see.
List Article Topics Returns the article topics the connection's own user can see.
Get Article Returns one article by id.
Create Article Publishes a knowledge base article into one or more channels. Cloning an existing article is how the same notice is rolled out to another property.
Update Article Changes an article, sending only the keys that should change.
Delete Article Deletes an article. Turning published off through the update operation withdraws it without losing the text.

Community

List Community Articles Returns the community pinboard posts. Hidden posts are left out by default, and a post counts as hidden when it is soft deleted or when every channel it was posted to is archived.
Get Community Article Returns one community post by id.
Create Community Article Posts to the community pinboard on a resident's behalf. Publish dates let a flow queue a notice for a date rather than posting it now.
Update Community Article Changes a community post, sending only the keys that should change.
Delete Community Article Removes a community post. Soft deleting keeps the record and only hides it, which is what a moderation flow should use.
List Community Article Comments Returns the comments on a community post.
Create Comment Adds a comment to a community post.
Update Comment Changes a comment. Turning published off is the moderation move that hides it without removing the thread.
Delete Comment Deletes a comment.
List Likes Returns the people who liked a community post or a comment.
Add Like Likes a community post or a comment as the connection's own user.
Remove Like Removes the connection's own like from a community post or a comment.

Files and Buckets

List Buckets Returns the file buckets the connection can see. A bucket is a document folder scoped to channels, which is how a house rules document reaches exactly one building.
Get Bucket Returns one bucket by id.
Create Bucket Creates a document folder. Its channels decide who can see it, and its locales narrow that further to speakers of a language.
Update Bucket Changes a bucket. Sending files here replaces the whole list rather than adding to it.
Delete Bucket Deletes a bucket.
List Bucket Files Returns the files in a bucket, optionally under one folder path.
Add File To Bucket Puts an already uploaded file into a bucket. The additive route, as opposed to replacing the whole list.
Rename Bucket File Renames a file inside a bucket. Routed through the bucket on purpose, so a channel write permission is enough.
Remove File From Bucket Takes a file out of a bucket. The file itself survives.
Upload File Uploads a file to Allthings and returns its id. Uploading only stores the file; it belongs to nothing until something references the id.
Get File Returns a file's metadata by id.
Delete File Deletes a file everywhere it appears.

Property Managers

List Property Managers Returns the property management companies the connection can see.
Create Property Manager Creates a property management company.
List Property Manager Users Returns the staff attached to a property management company.
Add User To Property Manager Attaches an existing user to a property management company.
Remove User From Property Manager Detaches a person from a property management company. The user account survives.
List Service Providers Returns the service providers a property management company works with, which is who external ticket work is dispatched to.

Property Manager Staff

List PM Users Returns property manager staff accounts across the account.
Get PM User Returns one property manager staff account by id.
Create PM User Creates a property manager staff account, which is how a joiner reaches the operations side of the app.
Update PM User Changes a property manager staff account, sending only the keys that should change.
Delete PM User Deletes a property manager staff account.
Set PM User Vacation Sets a staff member's absence and their deputy, so tickets route to somebody while they are away.

Organizations and Teams

List Organizations Returns the organizations, or the companies, on this account. Both are served from the same route and the type parameter chooses which.
Update Organization Changes an organization. Sending tenancies replaces the whole set it covers, and one setting decides whether its administrators can read every ticket raised by its members.
List Organization Users Returns the members of an organization.
Add Organization Users Adds existing people to an organization.
Remove Organization Users Removes people from an organization.
Add Organization Admin Makes one of an organization's members an administrator of it.
Get Organization Stats Returns counts for one organization: its members, teams and tenancies.
List Teams Returns the teams inside an organization. A team groups members and the tenancies they are responsible for.
Get Team Returns one team by id.
Create Team Creates a team inside an organization.
Update Team Changes a team. Sending users or tenancies replaces that whole list rather than adding to it.
Delete Team Deletes a team. The people and tenancies it grouped survive.

Responsible Contacts

List Persons Responsible Returns the named contacts residents are pointed at, for example a caretaker or an emergency plumber.
Get Person Responsible Returns one responsible contact by id.
Create Person Responsible Creates a responsible contact, which is how a new caretaker or contractor becomes visible to residents.
Update Person Responsible Changes a responsible contact.
Delete Person Responsible Deletes a responsible contact.

Taxonomy

List Tags Returns the tags defined on this account. A tag's name is a localized object carrying one label per language.
Create Tag Creates a tag, with its name supplied as an object keyed by language.
Update Tag Changes a tag.
Delete Tag Deletes a tag.
List Vocabularies Returns the vocabularies on this account. A vocabulary is a controlled list, such as the ticket categories.
List Vocabulary Terms Returns the terms in a vocabulary, including the built in lists as well as custom ones.
Create Term Adds a term to an editable vocabulary, with localized name and description.
Update Term Changes a custom term. Only terms in an editable vocabulary can be changed.
Delete Term Deletes a custom term. Allthings refuses while the term is still in use anywhere.

Custom Fields

List Custom Fields Returns the custom field values on one record, named by its type and its id.
Set Custom Field Sets a custom field value on a record. It is an upsert, creating the value when there is none and overwriting it when there is.
Delete Custom Field Removes a custom field value from a record. The preset itself survives.
List Custom Field Presets Returns the custom field definitions an owner has declared, which is where preset ids come from.

Notifications

List User Notifications Returns a person's in app notifications.
Mark Notification Read Marks one notification read or unread.
Mark Notifications Read Marks all of a person's notifications read up to a moment in time, in one call rather than one per notification.
Update Notification Settings Changes a person's notification preferences.

Search and Exports

Search Searches one kind of record by a query term, across articles, apps, groups, properties, units, organizations, tickets and staff.
List Exports Returns the CSV export jobs this connection has started.
Create Export Starts a CSV export. The job runs in the background, so a flow polls for its state rather than expecting data back.
Get Export Returns one export job's state. Polled after starting an export until the file is ready.
Download Export Downloads a finished export and stores the CSV in FlowRunner file storage, ready for a warehouse load or a reconciliation.
Delete Export Removes an export job from the list.

Communication Methods

List Communication Methods Returns the ways the connection's own user can be contacted.
Create Communication Method Adds a way to contact someone. Leaving the user empty adds it to the connection's own account.
Update Communication Method Changes a contact method.
Delete Communication Method Removes a contact method.

Frequently Asked Questions

What can FlowRunner do with Allthings?

FlowRunner agents can run Get Current User, Get My Minimal Data, and Get My Permissions in Allthings, plus 200 more actions.

Does connecting Allthings to FlowRunner require OAuth?

Yes. Allthings connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.

Can Allthings trigger a FlowRunner workflow automatically?

Allthings doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Allthings

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us