SendHQ
Send and receive email from your verified domains, manage templates and domains, and check deliverability from Claude.
- Brand
- Unknown
- Category
- Pending
- Primary Subcategory
- Pending
Integration details
Description
SendHQ is an email API and inbox for product teams and AI agents. This connector lets Claude work in your SendHQ workspace: read and search received and sent mail and threads, send email from your verified domains (single messages, batches, replies and attachments), manage drafts, hosted templates, labels and receiving addresses, add and verify domains and their DNS records, and investigate deliverability, bounces, complaints and suppressions. Tools that send real email or delete data are annotated as such, so you can require approval for them under Settings > Connectors > SendHQ. The connector uses its own API key, named after Claude, which you can delete under API Keys to disconnect. It cannot create or revoke API keys or change billing. Workspaces on the free integration trial can deliver only to the account email or AWS SES simulator addresses.
- Integration type
- Connector
- Verification status
Community connector- Platform
- Claude
- Category
- Pending
- Primary Subcategory
- Pending
- Secondary Subcategories
- None listed
- Brand
- Unknown
- Access
- Account required
- First tracked
- 2026-09-30
- Tool count
- 59
- Geography
- US
The broad Category that contains the Primary Subcategory.
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is listed.
Claude Connector discovery is coming soon
Community Connectors only appear in Claude’s registry.Once verified, organic discovery begins and we can calculate your score.Read more about Community Connector verification.
No spam. Unsubscribe any time.
No spam. Unsubscribe any time.
What discovery looks like

Claude can surface verified Connectors when they match a user’s Prompt.
How Claude Connector discovery works
Your Connector will compete to appear for users’ Prompts once Claude verifies it
Competitive lineup
59 tools agents can invoke
How do I improve a Community connector's discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.