Automation, security & integrations
Portal feeds & integrations
The platform talks to the portals and tools the agency already uses.
Used by: System
Kestrel Platform — IntegrationsSystem
| Connection | Direction | Schedule | Last run |
|---|---|---|---|
| Portal feed A | Outbound listings | On change | Today 09:02 — 38 live |
| Portal feed B (XML) | Inbound listings | Every 6 hours | Today 06:00 — 3 updated |
| Auction catalogue import | Inbound lots | Manual | 1 Sep — 3 lots |
| Image fetcher | Inbound media | With each import | Today 06:01 — 27 files |
How this works
Sends listings out to property portals and pulls data in from feeds and catalogues, on a schedule, with error reporting.
Who uses it
Marketing coordinator · Branch director
Step by step
- 1Listings are mapped to each portal's required fields and pushed when published or changed.
- 2Inbound feeds are polled on a schedule; changes create or update draft records for review.
- 3Images referenced by a feed are downloaded and stored locally so listings never depend on someone else's server.
- 4Failures are reported with the exact row and reason, and retried automatically.
Data captured
- Feed configuration and schedule
- Run history with created, updated, failed counts
- Stored image sets
Emails it sends automatically
- Feed run report
- Feed failure alert
Why it matters commercially
Portal listings stay accurate without anyone re-keying a price change on a Friday evening.
This screen is a faithful preview of a private area, filled with invented data. Nothing on it is editable here.