The CloudRadial AutomationAI SparkPost extension helps you support email sent through SparkPost: find out why a message bounced or never arrived, manage the suppression list, send a one-off transactional message, and check sending-domain authentication. This article covers what the extension can do, the API key and secrets it needs, which tools require approval, and the skills that ship with it. It is for workspace users who build automations (Admin or Owner Role).
- What the Extension Covers
- Creating the API Key
- Providing the Credentials to Your Runner
- Reads and Approval-Gated Changes
- Skills
- Tips for Working With SparkPost Data
What the Extension Covers
The extension calls the SparkPost REST API and provides 10 tools across four areas:
| Area | What you can automate |
| Delivery troubleshooting | Search message events such as deliveries, bounces, rejections, opens, and clicks, filtered by recipient, time window, event type, sending domain, or bounce class |
| Suppression list | Search suppression entries, look up one recipient, and add, update, or remove an entry |
| Transactional sends | Send a transactional email with inline content and read back a transmission by its id |
| Sending domains | List sending domains, read one domain's ownership and DKIM/SPF status, and ask SparkPost to re-check its DNS |
Install it from Extensions like any other catalog extension. See Browsing and installing extensions for the general install flow.
Creating the API Key
In SparkPost, go to Account > API Keys and create a key with the permissions for the areas you plan to use:
- Suppression Lists
- Message Events
- Transmissions
- Sending Domains
Grant read access, write access, or both for each, depending on what you want automations to do. For example, a key used only for delivery troubleshooting needs read access to Message Events and Suppression Lists. Copy the key when SparkPost shows it; it is a 40-character hexadecimal value.
Providing the Credentials to Your Runner
Store two secrets in your runner's Key Vault with these exact names:
| Secret | Value |
SparkPost-BaseUrl |
The SparkPost API base for your account: https://api.sparkpost.com/api/v1 for US accounts, or https://api.eu.sparkpost.com/api/v1 for SparkPost EU accounts |
SparkPost-ApiKey |
The API key you created in SparkPost |
Store the key exactly as SparkPost issued it, without a Bearer prefix. SparkPost expects the raw key as the authorization value, and the extension sends it that way for you. For how to add secrets, see Accessing and updating your runner's Key Vault.
Reads and Approval-Gated Changes
Sends and suppression edits change real state, so those tools pause the run for approval. The request appears as an Action Required item in the Inbox until someone approves it. See Handling Action Required items in the Inbox.
| Tool behavior | Tools |
| Approval-gated | Send a transactional email; add or update a suppression; remove a suppression |
| Runs without approval, but asks SparkPost to act | Re-verify a sending domain. This only asks SparkPost to re-check the domain's DNS records; it does not change your DNS or your SparkPost configuration. |
| Read-only | Search message events; search suppressions; look up one suppression; read a transmission; list sending domains; read one sending domain |
Removing a suppression lets SparkPost send to that address again, and adding one blocks future sends to it, so review the recipient carefully before you approve either.
Skills
The extension ships four skills that guide an agent through common SparkPost tasks:
| Skill | Use it to |
| Troubleshoot email delivery | Find out whether a message was delivered, bounced, or suppressed, and why. The agent searches message events for the recipient, reports the bounce class and reason for any bounce, and checks the suppression list if nothing was delivered. |
| Manage the suppression list | Search and review suppression entries, unblock a recipient who was suppressed, or suppress an address on request |
| Send a transactional email | Send a one-off message for a test or a manual notification, then report the transmission id and recipient counts |
| Check sending domains | Review each domain's verification and DKIM/SPF status, and ask SparkPost to re-check DNS after records were added |
Tips for Working With SparkPost Data
- Give times in UTC, for example
2026-09-14T00:00, when you ask for events in a specific window. If you give no window, the troubleshooting skill looks at the last few days. - The from address on a send must be on a verified sending domain
- A suppression applies to either the transactional or the non-transactional stream, so say which one when you ask an agent to suppress an address
- A message that never arrived but shows no bounce is often suppressed. Ask the agent to check the suppression list for that recipient.
If you are still having trouble, we’re here to help! Submit a ticket here for assistance, and don’t forget to check our status page to ensure there are no outages in your area.
Comments
0 comments
Please sign in to leave a comment.