Connect sign-in email domain
appAuthEmailConnectRun ONE connect pass for one owned app’s auth email — the dashboard’s own button. Requires confirmed: true, representing the human’s agreement to connect auth email for this exact projectId. It performs the single step the email provider’s last answer calls for: create the sending identity for send.<domain> if none exists, write the six records the identity names (into the customer’s own zone through the approval they gave at their DNS provider, or into a zone Tofu serves, else report them to be published by hand), or switch the app’s sending address once the provider says the domain is verified. It never writes half a configuration and never claims a step it could not confirm — a failure result does not establish that the change was applied. Repeat calls are safe: every step is idempotent at the provider, and the records it cannot write are returned for a human. It needs the app to be deployed and to have its own database.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"projectId": "<projectId>",
"confirmed": "<confirmed>"
},
"name": "appAuthEmailConnect"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| confirmed | Yes | ||
| projectId | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| dns | Yes | ||
| state | Yes | ||
| domain | Yes | ||
| sender | Yes | ||
| appName | Yes | ||
| enabled | Yes | ||
| message | Yes | ||
| records | Yes | ||
| siteUrl | Yes | ||
| identity | Yes | ||
| nextSteps | Yes | ||
| observedSender | Yes |