Prepare accounts and email access
Supply the account and mailbox inputs required by your chosen automation.
Account resources identify the accounts a workflow should use. A workflow that reads a sign-in code or link also needs working mailbox access. Your Titan login, an app account, and its mailbox connection are separate credentials.
Prepare an account record
- Choose the strategy and read its required resource types with your assistant.
- Check whether the intended account is already saved.
- Provide the fields required by that exact type, such as the account identity and any required login details.
- Store passwords or tokens in the designated secret fields.
- Have the assistant read back the non-secret identity and confirm which row will be used.
Use Resources to inspect the visible content afterward. Account management happens through MCP; the Resources page does not provide an account import form.
For a batch, ask the assistant to validate the required fields and identify duplicates before writing. Keep the result tied to the original account identities so you can review which records were created or changed.
Prepare mailbox access when required
Ask the assistant which mailbox connection the selected strategy expects. Use the authentication method supported for that mailbox, such as provider authorization or an application-specific credential where applicable.
An email address alone does not authorize Titan to read a mailbox. A website password is not automatically a valid mailbox credential either. If the required authorization flow is not available to you, ask your Titan administrator to help set it up.
Keep mailbox credentials out of topics, descriptions, screenshots, and support messages. Ask the assistant to report connection status without repeating passwords, authorization codes, or tokens.
Before starting login automation
- Confirm the selected app account and mailbox belong together.
- Check that the mailbox authorization is current.
- Complete any phone-side sign-in or verification requirement identified by the workflow.
- Confirm the account is not already held by another run.
Some account resource types are exclusive during execution. If Titan reports Account is currently in use, inspect the existing run or queue instead of duplicating the account to work around it.
A code or sign-in link does not arrive
Check the account identity, mailbox connection, and the actual provider's delivery. Inspect the relevant attempt in My Runs to distinguish waiting for email from an authentication or device failure.
Before restarting a login flow, check whether the original attempt is still active. Reauthorize an expired mailbox connection using the method supplied for that account, then retry only the intended work.