Commerce and support teams
Confirm Stripe receipt delivery with SendGrid and Slack
Check whether payment receipts left SendGrid, then alert Slack when bounces spike.
Outcome: A delivery-status brief for transactional mail without sending new email
Example questions
Try asking your AI client
-
Pull recent Stripe payment receipts, then check SendGrid delivery stats for today and list bounces in the last 6 hours. If bounce count is up, search Email Activity for those recipient addresses, summarize status and bounce reason (not full bodies), and post a short alert to our payments Slack channel. Do not send email.
-
Did Jack's Stripe receipt email bounce in SendGrid, and should I warn #payments in Slack?
-
Compare today's Stripe successful charges with SendGrid delivery failures, then draft a Slack alert - do not post it if nothing is wrong.
-
Give me a morning deliverability brief: Stripe receipts sent, SendGrid bounces, and whether Slack needs a heads-up.
-
A customer says they never got a receipt. Check Stripe, SendGrid events, and write a Slack note for #payments. Do not email the customer.
The problem
Stripe records a successful charge. Customers still write in when the receipt never arrives. Chat tools show the payment, not whether SendGrid delivered the mail.
Gateway tools
stripepayment or invoice tools for the charge contextsendgrid__get_statsfor delivered, opens, clicks, and bouncessendgrid__list_bouncesfor the suppression windowsendgrid__search_messagesorsendgrid__get_messagewhen a recipient needs event historyslack__send_channel_messagefor a redacted summary
Use describe-service-tool to confirm SendGrid, Stripe, and Slack are connected before dispatching.
Governance
- SendGrid results include recipient addresses and subjects. Prefer message IDs, event types, and counts in Slack.
- This integration cannot send mail or delete suppressions. Do not ask the agent to resend a receipt through SendGrid.
- Email Activity tools need the SendGrid add-on. Stats and bounces still work without it.
- Audit logs record tool calls. Keep
limitsmall during incidents.
Connect via private gateway
Activate the integrations above, create an API token scoped to mcp:private-gateway, then add this config to your MCP client.
Config file: ~/.cursor/mcp.json
{
"mcpServers": {
"stackgate-private-gateway": {
"url": "https://stackgate.ai/mcp/private",
"headers": {
"Authorization": "Bearer YOUR_API_TOKEN"
}
}
}
}