Flatfox
E-commerceConnect AI agents to Flatfox, the Swiss rental and sale marketplace and property management platform. Agents read public listings and similar-property matches, pull tenant applications and inventory, and update the status of a property ticket.
What This Integration Enables
Flatfox is two things at once, a public rental and sale marketplace in Switzerland and the property management platform behind the agencies listing on it, and this connector reflects that by being almost entirely a read surface. That is not a limitation to apologise for, it is the accurate description of what an agency can safely automate. On the marketplace side, List Public Listings returns the published catalogue with filters for agency, project, listing keys and status, Get Public Listing returns one listing in full with price, address, coordinates, attributes, images, documents and the publishing agency, and Get Similar Listings returns what the catalogue considers comparable. On the managed side, List Listings and Get Listing cover your organization's own listings across every status, and the inventory sits behind them: properties group houses under a management reference, houses are single addresses, and objects are the individual rentable units such as apartments or parking spaces. Applications, users, contacts, members, labels and label types round it out, and Get Organization tells a flow which agency the token belongs to.
One action writes. Update Ticket Status sets an existing ticket to open, solved or archived, and can optionally update the ticket's title and description in the same call. That is the entire write surface of this connector, and building on it deliberately is the point. Everything else an agent does here informs a decision rather than making one, which suits property management well: the expensive mistakes in this domain are made when somebody acts on a partial picture, not when they read too much. Three practical notes shape a flow. Public listing reads work without a token at all, while organization data requires a scoped one, so a market monitoring flow and a portfolio flow have genuinely different access requirements. The token itself is created per organization under account settings and is scoped read or read and write there, which is where the real permission decision is made rather than in the connector. And there is a realtime trigger, On Flatfox Event, which creates a Flatfox event subscription pointing at the flow's callback URL and removes it when the trigger is removed. Agents assemble the picture. The one change a tenant can feel is where human-in-the-loop oversight belongs.
Without FlowRunner
With FlowRunner
Use Case Scenarios
A maintenance report that arrives with its history attached
A tenant reports a fault and Flatfox raises a ticket. On Flatfox Event fires, and rather than pushing a notification with a subject line, the agent builds the case. Get Ticket returns the requester, the assigned agent, the status, the description and the attachments the tenant uploaded. Get House and Get Property resolve the address and the management reference it sits under, and List Tickets filtered by that house surfaces what else is open or was recently solved there, which is how the third report of the same leak stops being triaged as a first report. List Members and List Labels supply who is available and how the organization classifies work. What reaches the property manager in Slack is a short brief: the fault, the address, the two related tickets from the last six weeks, the photos, and a proposed status change. The agent does not change the status itself.
A viewing list built from the whole application set
Applications against a listing arrive over days and are usually read one at a time, which makes it hard to see the shape of the response. On a schedule, or when an application created or submitted event fires, the agent calls List Applications for the organization with the applicant and listing expanded, and Get Application for anything needing detail. It groups by listing, resolves the listing through Get Listing and the address through Get House, and produces the view a letting agent actually works from: how many applications per listing, how long the oldest has waited, which listings have none. That summary goes to the letting team and, where the agency keeps its scheduling elsewhere, the shortlist writes to a base in Airtable so viewings are booked from one list rather than from an inbox. Nothing about an application is written back through this connector, which keeps the decision about who gets a home where it belongs.
Watching the market without a token
Public listing reads do not require organization access, which makes a market monitoring flow cheap to run and easy to scope. On a schedule the agent calls List Public Listings filtered by agency slug, project or status across the segments it cares about, and Get Public Listing for the detail on anything new, capturing price, address, coordinates and attributes. Get Similar Listings turns a single property into a comparison set, which is the input a pricing conversation with an owner needs. The results land in a sheet in Google Sheets with the date attached, so a month of runs becomes a price history rather than a snapshot, and a listing that changes status from published to reserved is visible as a change rather than as an absence.
Human-in-Loop Highlight
Update Ticket Status is the only write in this connector, so it is the only thing to gate, and it turns out to deserve the attention on its own merits. Two properties make it consequential. The first is that its statuses are tenant facing in effect if not in wording. Marking a maintenance ticket solved asserts that somebody's heating works, and the person best placed to disagree is the person living in the flat. Archiving it removes the ticket from the working queue entirely, which is a reasonable action for a duplicate and a bad one for a report that simply had not been picked up yet. The second is quieter and is the reason a rule cannot be trusted here: this action optionally updates the ticket's title and description in the same call. Those fields hold the tenant's own account of the problem, in their words, and there is no version history exposed anywhere in this connector to recover them from. An agent that tidies a description into a neater summary while closing the ticket has overwritten the only first hand record of what was reported, and the loss is invisible because the ticket afterwards looks better than it did before. Both of those risks point the same way. The agent may read everything and write nothing. So it assembles the case with Get Ticket for the current record and its attachments, List Tickets filtered by the same house for the pattern, Get House and Get Property for the address and the management reference, and List Members for who is assigned, then posts to the property manager in Slack: "Ticket 2214, Bergstrasse 12, apartment 3B. Reported by the tenant 9 days ago: 'Wasser lauft aus dem Heizkorper im Wohnzimmer', 2 photos attached. Assigned to Nadia. 2 related tickets on this house in the last 6 weeks, one solved 4 weeks ago with the same description. Contractor visit was logged in the notes yesterday. Proposed: set to solved. Update Ticket Status can also overwrite the title and description, and the original wording is not recoverable through the API, so the tenant's text will be left exactly as written. Mark solved, leave open pending tenant confirmation, or archive as a duplicate of 2103?" A person answers once, the agent sets only the status that was released, and it never sends the optional title and description fields at all unless a person supplied the replacement wording themselves. This is the digital andon cord placed on a connector with exactly one write, which is the case where it is easiest to skip and least defensible to.
Agent Capabilities
23 actionsListings
5- List Public Listings Returns published rental and sale listings from the public catalogue, paged, with filters for organization slug or ID, project, listing keys and status covering pre, act, dis, arc and rem. Use the expand argument to inline related objects such as the cover image. Public listing reads work without a token.
- Get Public Listing Returns the full public detail of one listing by its primary key, including price, address, geo coordinates, attributes, images, documents and the publishing agency.
- Get Similar Listings Returns the listings the catalogue considers similar to a given public listing, which is the comparison set a pricing conversation is built from.
- List Listings Returns your organization's own managed listings across all statuses, paged. Requires a token with read access, unlike the public catalogue.
- Get Listing Returns a single managed listing owned by your organization by its primary key.
Inventory
6- List Houses Returns the houses in your organization's inventory, meaning single addresses within a property, paged. Expand property, branch and roles to inline the owning property and its assigned users.
- Get House Returns a single house by its primary key, including its address and property reference.
- List Properties Returns the properties in your organization's inventory, paged. A property groups one or more houses under a single management reference.
- Get Property Returns a single property by its primary key.
- List Objects Returns the rentable objects in your organization's inventory, meaning individual units such as apartments or parking spaces, paged.
- Get Object Returns a single rentable object by its primary key.
Tickets
3- List Tickets Returns support and maintenance tickets in your organization, paged, filtered by agent assignment, status, associated house or full text search, and ordered by a chosen field. Filtering by house is how a repeat report becomes visible as a repeat.
- Get Ticket Returns a single ticket by its primary key, including the requester, the agent, the status, the description and the attachments.
- Update Ticket Status Sets an existing ticket to open, solved or archived, and can optionally update the ticket's title and description in the same call. This is the only write in the connector, and the optional description update overwrites the reporter's own wording with no recoverable history.
Applications
2- List Applications Returns the rental applications submitted to your organization's listings, paged. Use expand to inline the applicant or the listing, and ordering to sort the set.
- Get Application Returns a single rental application by its primary key, including applicant details and the listing it belongs to.
Users
3- List Users Returns the users visible to your organization, paged, filtered by one or more email addresses or user keys.
- Get User Returns a single user by email address, including name and avatar. Expand photo to inline the full image object.
- List Contacts Returns the contacts stored in your organization's CRM, paged.
Organization
4- Get Organization Returns the organization, meaning the agency your API token belongs to, including its name and address. Useful as a first call to confirm which agency a connection is scoped to.
- List Members Returns the members, meaning staff users, of your organization, paged.
- List Labels Returns the labels attached to your organization's listings and applications, such as a contact request or a created checklist, paged and filterable by listing IDs.
- List Label Types Returns the set of label types defined for your organization, each with its display text and colours.
Triggers
1 triggersEvent Triggers
1- On Flatfox Event Fires when a chosen Flatfox event occurs in your organization. The trigger creates a Flatfox event subscription pointing at the flow's callback URL and deletes it when the trigger is removed, so there is no orphaned subscription left behind. Supported events cover listings, including published, prepublished, created, disabled, removed, archived, reserved and unreserved, applications, including created, submitted, chosen, rejected and removed, tickets, including created, updated and resolved, and message and note creation. Flatfox event subscriptions have no documented signature mechanism, so deliveries are matched to a trigger only by the connection ID in the callback URL. Treat an inbound event as a prompt to re read the record with Get Ticket, Get Application or Get Listing rather than as evidence in itself.
Frequently Asked Questions
What can FlowRunner do with Flatfox?
FlowRunner agents can run List Public Listings, Get Public Listing, and Get Similar Listings in Flatfox, plus 20 more actions.
Does connecting Flatfox to FlowRunner require OAuth?
No. Flatfox connects to FlowRunner with an API key, no OAuth flow required.
Can Flatfox trigger a FlowRunner workflow automatically?
Yes. Flatfox supports 1 trigger that can start a FlowRunner workflow automatically.
Start building with Flatfox
$100 in credits. No card required. Connect in minutes.