Useful things to ask for

Read these Letted guides first:
https://app.letted.com/docs/creating-tenancies
https://app.letted.com/docs/api-reference

If you cannot open them, ask me to paste the pages rather than guessing.

When I mark a tenancy as agreed in [my other system], I want to create
it in Letted at the correct existing property or room.

Transfer the dates, monthly rent, deposit details and everyone in the
tenant group. Keep the people together in one request and identify the
lead tenant. Keep portal access off and do not send any invitations.

Use an external reference so we can find the record again. Make retries
safe so a connection problem cannot create the same tenancy twice.
Show me how we will confirm that the record and its follow-up setup succeeded.

Read these Letted guides first:
https://app.letted.com/docs/property-tasks
https://app.letted.com/docs/api-reference

If you cannot open them, ask me to paste the pages rather than guessing.

When someone submits a repair report in [my reporting system], create
a Maintenance task at the correct property in Letted.

Use a clear title and include the description from the report. Ask me
how to map urgency to Low, Medium, High or Urgent. Store the report's
reference and make retries safe. Return the task ID so we can track it.
Do not assign a contractor, approve spending or mark the task complete.

Read these Letted guides first:
https://app.letted.com/docs/tenant-access
https://app.letted.com/docs/api-reference

If you cannot open them, ask me to paste the pages rather than guessing.

I want to add tenants to Letted now but invite them later.
Explain a two-stage process: first create their records with portal
access disabled; then, after I approve, enable access and request an
invitation for each eligible tenant.

Check the email address and whether they already have a linked account.
Show how the connection will check whether an invitation was accepted
by the email provider. Do not treat a queued invitation as a sent email.

Read these Letted guides first:
https://app.letted.com/docs/receiving-events
https://app.letted.com/docs/api-reference

If you cannot open them, ask me to paste the pages rather than guessing.

I maintain a tracker in [my other system]. When an agreement is completed
in Letted, update the matching entry in that tracker.

Use the agreement.completed event and its tenancyId to find the entry.
Read the agreement status before marking it signed: fully_signed means
signatures are complete; completed with signatureRequired false is an
unsigned form, not a signed contract.
Explain what the receiving system must support. Verify Letted's signature,
ignore duplicate events and allow for events arriving out of order.
Do not email tenants or change the tenancy as part of this workflow.

Read these Letted guides first:
https://app.letted.com/docs/property-tasks
https://app.letted.com/docs/receiving-events
https://app.letted.com/docs/api-reference

If you cannot open them, ask me to paste the pages rather than guessing.

I want my other system to follow Maintenance tasks created in Letted.
Use task.created and task.status_changed, filtering category to Maintenance.
Update the tracker when a task completes and when it reopens.
Fetch the latest task record before deciding its current state.
Explain which permissions and property access the connection needs.

Read these Letted guides first:
https://app.letted.com/docs/getting-started
https://app.letted.com/docs/api-reference

If you cannot open them, ask me to paste the pages rather than guessing.

Before building this connection, give me a short checklist:
1. What will trigger it?
2. What exact information will it read or change?
3. Which property and people will be affected?
4. Will it send any emails?
5. How will it avoid duplicates and report failures?
6. How do I stop it?

Use placeholders and fictional details. Show me the proposed request
before anything is sent to my live Letted account.