SMTP2GO
MESSAGING · MESSAGING
Email and SMS sends, scheduled sends, activity search, and reports on their key.
Connect SMTP2GO with Fabriq Developer
Your user pastes their SMTP2GO credential on a page Agentic Fabriq hosts, so it never reaches your backend and never becomes one shared key across all of your users. Same call as OAuth, one more argument.
Provider names are surfaces, not vendors, and the authoritative list is the capabilities endpoint rather than any page including this one — an unknown name returns 400 with the valid list. Fabriq Developer is free to start and needs no provider paperwork. Start free or read the quickstart.
Connecting SMTP2GO in practice
SMTP2GO lets you set a rate limit on each individual API key in Sending > API Keys, so the ceiling an agent hits is whatever someone typed into the dashboard, and over it the API answers "API key ratelimit exceeded". The one figure SMTP2GO publishes globally is /activity/search at 60 per minute.
Scopes that draw scrutiny
API key (Sending > API Keys)The per-key rate limit set here is the main restriction mechanism, so two keys on the same account can behave very differently under load.
Rate limits
- The /activity/search endpoint "has a rate limit of 60 per minute".
- Individual rate limits can be set per API key; exceeding one returns the error "API key ratelimit exceeded".
- Over the limit the API returns 429, and the originating IP "will be timed out for an indeterminate amount of time, no less than 1 minute".
- Free plan sending: 1,000 emails per month, a maximum of 200 per day, and 25 per hour while no sender domains are verified.
- New accounts are held to 1,000 emails per day during the review period.
Worth knowing
- The IP timeout after a 429 is explicitly indeterminate, with only a one-minute floor, so there is no reset time to schedule against.
- Sending allowances and API rate limits are two separate meters: you can be inside the per-key request limit and still be refused because the daily email cap is spent.
- A brand-new account is under review and capped well below plan, so load testing on a fresh account measures the review cap rather than the plan.
Checked against Rate limiting (2026-09-29), SMTP2GO developer documentation (2026-09-29)
What an agent can do
Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.
Often connected alongside
Put SMTP2GO behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.