Fix it|Tool troubleshooting
Fix: Email automations
Automations need SMTP or integrated email providers configured in Settings. Silent failures usually mean mail is not leaving the server.
Primary path in the app: /admin/automations
/admin/automationsTip
Work in order from top to bottom. If nothing here matches, capture the exact error text, URL, time, and account role, then ask your studio owner or Contact with those details.
Members not receiving automation email
- Open Settings and verify SMTP host, port, user, and from-address; send a test message from there.
- Confirm the automation toggle is on and the template is not paused.
- Check spam for the studio domain reputation; add SPF/DKIM at your DNS host if your IT team requires it.
Wrong content sent
- Re-read the template body in Automations; save again after edits.
Note
These articles describe the Fitoa product surface. Hosted behaviour also depends on your deployment environment (database, SMTP, Stripe, and signup flags). Your owner or host can confirm values in .env when a panel says something is not configured.
Important
Never paste live passwords or API keys into public AI chats. Use Settings test buttons or your host’s secure channels only.