Send property, request, contract, invoice, payment and maintenance emails
Use the send action from the source record.
Before you start
Use the relevant record permission. Workspace mail, branding and API configuration require administrative access.
Follow these steps
- Open the source record or configuration named in the route.
- Use the send action from the source record.
- Mail uses the workspace’s configured transport and recipient context. Tenant SMTP/OAuth is preferred; where supported, platform SMTP can supply transport with the tenant reply-to. A saved or marked-sent record does not prove inbox delivery; check the delivery result before resending.
- Generate, preview or save the required output and inspect its actual result.
Fields, rules and limits
- Mail uses the workspace’s configured transport and recipient context. Tenant SMTP/OAuth is preferred; where supported, platform SMTP can supply transport with the tenant reply-to. A saved or marked-sent record does not prove inbox delivery; check the delivery result before resending.
Check it worked
The actual output belongs to the intended workspace and source record.
If something does not look right
If the expected result is missing, check the saved record, the current workspace and the action’s permissions. Record the exact validation message; do not repeat a state-changing action until you know whether the first attempt saved.
Questions and answers
What should I verify for this task?
Mail uses the workspace’s configured transport and recipient context. Tenant SMTP/OAuth is preferred; where supported, platform SMTP can supply transport with the tenant reply-to. A saved or marked-sent record does not prove inbox delivery; check the delivery result before resending.
Why is the record or action unavailable?
Use the relevant record permission. Workspace mail, branding and API configuration require administrative access. Check the current company and record relationship before requesting additional access.