Re-Leased is a cloud property-management platform engineered specifically for commercial property — office, retail, industrial, and mixed-use portfolios. Unlike residential-first platforms that bolt on a commercial module as an afterthought, Re-Leased was designed from the ground up around the commercial lease lifecycle: critical date tracking, rent reviews, CPI/RPI escalations, outgoings reconciliation, arrears management, and multi-property owner reporting.
Commercial landlords operate in a fundamentally event-driven world. A lease for a retail tenancy may contain a rent review every two years tied to CPI, a landlord break option at year five, a make-good obligation at expiry, and a personal guarantee that lapses 90 days before the lease end. Miss any one of these dates and the financial or legal consequence is real — a below-market rent locked in for another review cycle, a break option waived by silence, or a fitout stripped without a make-good payment.
Security, compliance, and vendor evaluation frameworks for AI operations
Automate document collection, deadline tracking, and stakeholder updates
Real-time dashboard showing deal progress and expected commissions
Discover how Re-Leased powers real estate automation workflows
Store and manage the full commercial lease record: lease terms, rent escalation schedules (fixed, CPI, market), option periods, break clauses, lease expiries, and critical notice dates. All dates are tracked on a central calendar with configurable lead-time alerts.
A missed rent review or break option notice can lock in a below-market rent for years or forfeit a landlord's right to terminate. Re-Leased's critical-date engine is the source of record for every structured event in the tenancy — automate 90-day, 60-day, and 30-day alerts to the property manager and solicitor before any contractual date falls due.
Get a personalized plan for your tech stack
Ready-to-deploy workflows powered by Re-Leased + NextAutomation
Ninety days before a commercial lease expiry, the automation surfaces the tenancy to the property manager with a structured action brief: current rent versus estimated market, break clause status, tenant payment history, and a recommended course of action (renew, renegotiate, or begin vacancy preparation). This window gives the team time to act before the tenancy expires by default.
1n8n scheduled trigger fires each morning
2Query Re-Leased API for all active tenancies with lease_end_date between today and today + 90 days
3For each expiring tenancy, retrieve: current rent, payment history (arrears last 12 months), any existing option or renewal clause from the lease record
4Pull comparable market rents from your market data source or an internal comparables log to calculate face-rent gap
Property managers receive a structured, data-grounded action brief 90 days before every commercial lease expiry — not a calendar reminder that requires them to assemble the context themselves. Vacancy surprises become structurally impossible when this workflow is active.
Connect Re-Leased to your workflows with powerful triggers and actions
Fires when a tenancy's lease end date falls within a configurable lead-time window (e.g., 90, 60, or 30 days) as detected by a scheduled API query against Re-Leased's tenancy data.
When a commercial lease is 90 days from expiry, surface the tenancy to the property manager with current rent, tenant payment history, and a recommended renewal or vacancy-preparation brief.
Fires when a scheduled rent review date is within the lead-time window, pulled from the Re-Leased tenancy record's review schedule.
60 days before a CPI rent review, fetch the current index figure, calculate the proposed new rent, draft the tenant review notice, and route to the property manager for approval.
Fires when an outstanding invoice in Re-Leased crosses the overdue threshold — detected by polling the invoice API for outstanding status and due date comparison.
When a tenant's rent invoice is 7 days overdue, initiate the arrears recovery sequence: draft a courtesy reminder at day 7, formal demand at day 14, and solicitor referral flag at day 30.
Fires when a new lease record is created in Re-Leased via the API, indicating a new tenant has been onboarded to the property.
When a new commercial tenancy is created, automatically send the tenant a welcome pack with payment instructions, building access information, and a maintenance-request link.
Fires when a maintenance work order in Re-Leased is updated — created, assigned to a contractor, or marked complete.
When a work order is marked complete, notify the tenant that the maintenance issue has been resolved, request a satisfaction confirmation, and log the response against the property maintenance record.
Scheduled trigger aligned with the owner statement cycle — pulls the Re-Leased monthly ledger data for each property on a fixed schedule.
On the last business day of the month, pull all owner statements from Re-Leased, generate an AI-written commentary for each, and deliver branded reports to landlords automatically.
Write new tenancy data to Re-Leased or update an existing tenancy record — lease dates, rent amounts, review schedules, and tenant contacts — via the Re-Leased API.
When a new lease is executed in DocuSign, automatically create the Re-Leased tenancy record with the agreed rent, lease dates, review schedule, and tenant contact details extracted from the signed document.
Programmatically create a rent invoice, outgoings charge, or ad-hoc fee in Re-Leased for a specific tenancy.
After a rent review is agreed and confirmed, write the new rent amount to Re-Leased and create the first invoice at the reviewed rate without requiring manual entry in the platform.
Create a new maintenance work order in Re-Leased from an external source — a tenant email, a structured request form, or a building inspection finding.
When a tenant submits a maintenance request via a web form, automatically create the corresponding Re-Leased work order, assign it to the appropriate contractor, and send the tenant a confirmation with a reference number.
Add a note to a Re-Leased tenancy record via the API, creating an audit-trail entry for any automated action taken (arrears email sent, review notice dispatched, owner statement delivered).
After sending an arrears recovery email, log the communication in the Re-Leased tenancy notes with timestamp and escalation tier so any property manager reviewing the file can see the complete recovery history.
Write an updated rent figure to a Re-Leased tenancy record following a completed rent review — updating the invoicing schedule for future periods.
Once a CPI rent review is agreed and confirmed in writing, push the new rent amount to Re-Leased via API so the next invoice is automatically generated at the correct figure without a manual platform entry.
Get started in approximately 30 minutes for API credential setup and first test call; 2-3 hours for lease expiry and arrears workflows; 1 day for full owner statement automation with AI commentary
Log in to your Re-Leased account and navigate to the Settings or Developer section to locate your API key or OAuth application credentials. If API access is not visible in your account, contact Re-Leased support to confirm it is enabled for your plan. Record the base API URL, authentication method (Bearer token or API key header), and any rate-limit documentation provided.
Re-Leased also offers a Zapier integration for common triggers and actions. If your workflows are relatively straightforward (e.g., new tenancy created → send welcome email), starting with Zapier lets you validate the logic quickly before building custom n8n workflows for more complex multi-step sequences.
In n8n, create a new HTTP Request credential for Re-Leased: store the base API URL and the Bearer token (or API key) in the credential store — never in workflow nodes directly. Test the credential by making a simple GET request to the tenancies endpoint and confirming you receive a list of your active properties and leases.
Map out the Re-Leased data schema before building workflows. Understand how Re-Leased structures tenancy IDs, property IDs, and invoice IDs so your n8n workflows reference the correct identifiers when chaining API calls. A 30-minute API exploration session with Postman or the n8n HTTP Request node will save hours of debugging later.
Start with the lease expiry alert — it is the lowest-risk, highest-value workflow to validate the Re-Leased API connection. In n8n, create a scheduled trigger (daily at 8:00 AM), add an HTTP Request node to GET /tenancies with a lease end date filter, and add a second node to send a Slack message or email listing any tenancies expiring within 90 days. Run it once manually and confirm the tenancy data is correct.
Use the n8n 'Split In Batches' node if your portfolio has more than 50 tenancies, to avoid hitting Re-Leased API rate limits in a single polling request. Process tenancies in batches of 25 with a short pause between batches.
Create a daily scheduled workflow that queries Re-Leased for all outstanding invoices with a due date more than 7 days in the past. Group by tenancy, calculate days overdue and total arrears balance, and route to the appropriate escalation action (email draft, formal letter, or solicitor referral flag). Test against a sample tenancy where you know an invoice is outstanding before activating across the full portfolio.
Log every arrears action back to Re-Leased as a tenancy note via the API. This creates an automated audit trail in Re-Leased itself — so any property manager looking at the tenancy record can see exactly when each recovery step was taken, without checking a separate system.
Set up the monthly owner statement workflow: schedule to trigger on the last business day of the month (using n8n's CRON node with a date-based condition), pull the Re-Leased owner statement data via API for each managed property, pass the figures to an AI node for commentary generation, and assemble the final package using a document-generation tool or a structured email template. Test with a single property owner before activating for the full portfolio.
Owner statement delivery is a high-trust communication. Build a 24-hour delay into the workflow between statement generation and delivery — giving the property manager a window to review and flag any anomalies before the statement reaches the landlord. A simple n8n 'Wait' node plus a Slack notification achieves this review gate.
Once the core Re-Leased workflows are running reliably, connect the downstream outputs: push net income figures from owner statements to your portfolio tracking spreadsheet or Airtable register, feed arrears data to your KPI dashboard, and link rent-review outcomes to your underwriting model to keep yield projections current. This is where Re-Leased transitions from a standalone property-management tool into the live data backbone of your CRE operating system.
Build a central property-ID mapping table that links Re-Leased property IDs to your internal asset names, deal codes, and any investor-portal identifiers (Agora, InvestNext, etc.). This lookup table is the glue that allows a Re-Leased event to trigger the correct downstream update in every other system without hard-coding IDs in every workflow.
Common questions about Re-Leased integration
Explore other tools that work great with your workflow
Get a free AI roadmap showing how to connect Re-Leased with your existing tools for maximum impact.
Get Your Free AI Roadmap