API & future integrations
Scope automation without depending on connections that are not yet available.
This guide describes the planned workflow and what you can prepare today. These services are not yet enabled on this website.
Before you begin
- This website does not offer a public API or external email connection.
- Endpoints, authentication, quotas and events will be published alongside the relevant service.
Step by step
- 01
Describe the scenario
Identify the trigger, inputs, outcome and person responsible for failures. Start with one measurable workflow.
- 02
Prepare the data contract
List genuinely necessary fields, access rights and retention periods. Use fictional examples when discussing a connection.
- 03
Plan for failures
Define expected behaviour for duplicates, delays, rejection and interruption. Provider acceptance does not prove that a recipient received a message.
Practical example
Scenario to scope: request received → unique record → team notification → processing follow-up. This describes a requirement, not an available API.
Review checklist
- The scenario depends on no invented endpoint.
- Secrets stay out of forms and browsers.
- An owner and recovery behaviour are defined.
Troubleshooting
Where can I find an API key?
This website does not distribute public API keys. Describe your needs in a contact draft to prepare a future integration.
Can I connect Gmail or Outlook?
Provider choice and incoming-mail processing still need integration. No account is currently connected and no synchronisation is active.
Keep exploring
Still missing an answer?
Prepare a question for the team