一键导入
mailtrap-managing-contacts
Manage Mailtrap contacts, lists, segments, custom fields, imports, CRM syncs, and campaign audiences through the UI or API.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Manage Mailtrap contacts, lists, segments, custom fields, imports, CRM syncs, and campaign audiences through the UI or API.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Configure or troubleshoot Mailtrap live email sending with Email API, SMTP, transactional streams, bulk streams, or batches.
Add or verify a Mailtrap sending domain, troubleshoot DNS propagation, publish SPF/DKIM/DMARC records, and complete compliance.
Find, compare, adapt, and design bounded AI-agent feedback loops with explicit checks, stop rules, guardrails, and handoffs.
| name | mailtrap-managing-contacts |
| description | Manage Mailtrap contacts, lists, segments, custom fields, imports, CRM syncs, and campaign audiences through the UI or API. |
| risk | safe |
| source | community |
| date_added | 2026-06-19 |
Before generating API request bodies: check the Contacts OpenAPI spec for current field names, required parameters, and nested structures.
Contacts are the marketing database: lists, segments, custom fields, and imports for campaign audiences and related workflows. The Contacts API automates create/update and can feed CRM or CDP sync (your code, or tools like Zapier, Make, n8n — see Import contacts).
Suppressions (hard bounces, spam complaints, unsubscribes on the sending side) live in the sending product and block delivery for those addresses on your streams. That is applied separately from marketing filters (segments, list membership, consent flags) that decide who is eligible for campaigns. For sending-side blocks, see Suppressions and mailtrap-sending-emails.
Related skills: mailtrap-sending-emails (live send paths).
All endpoints below need Authorization: Bearer $MAILTRAP_API_TOKEN and an $MAILTRAP_ACCOUNT_ID in the path. Resolve $MAILTRAP_ACCOUNT_ID from GET https://mailtrap.io/api/accounts, and store tokens in environment variables or a secrets manager.
| Action | Method | URL | Reference |
|---|---|---|---|
| Create / get / update / delete contact | various | https://mailtrap.io/api/accounts/$MAILTRAP_ACCOUNT_ID/contacts | Contacts |
| Bulk import (async job) | POST | https://mailtrap.io/api/accounts/$MAILTRAP_ACCOUNT_ID/contacts/imports | Bulk import |
| Contact lists | various | https://mailtrap.io/api/accounts/$MAILTRAP_ACCOUNT_ID/contacts/lists | Contact lists |
| Custom fields | various | https://mailtrap.io/api/accounts/$MAILTRAP_ACCOUNT_ID/contacts/fields | Contact fields |
| Custom events | POST | https://mailtrap.io/api/accounts/$MAILTRAP_ACCOUNT_ID/contacts/{contact_identifier}/events | Contact events |
| Export contacts | various | https://mailtrap.io/api/accounts/$MAILTRAP_ACCOUNT_ID/contacts/exports | Export contacts |
GET .../contacts/imports/{import_id}. See Bulk import.curl)curl -X POST "https://mailtrap.io/api/accounts/$MAILTRAP_ACCOUNT_ID/contacts" \
-H "Authorization: Bearer $MAILTRAP_API_TOKEN" \
-H 'Content-Type: application/json' \
-d '{
"contact": {
"email": "john.smith@example.com",
"fields": {"first_name": "John", "last_name": "Smith", "company": "Example Inc"},
"list_ids": [1, 2, 3]
}
}'
curl -X POST "https://mailtrap.io/api/accounts/$MAILTRAP_ACCOUNT_ID/contacts/imports" \
-H "Authorization: Bearer $MAILTRAP_API_TOKEN" \
-H 'Content-Type: application/json' \
-d '{
"contacts": [
{"email": "user1@example.com", "fields": {"first_name": "John"}, "list_ids_included": [1, 2]},
{"email": "user2@example.com", "fields": {"first_name": "Jane"}, "list_ids_included": [1]}
]
}'
curl -X POST "https://mailtrap.io/api/accounts/$MAILTRAP_ACCOUNT_ID/contacts/{contact_identifier}/events" \
-H "Authorization: Bearer $MAILTRAP_API_TOKEN" \
-H 'Content-Type: application/json' \
-d '{"name": "UserLogin", "params": {"user_id": 101, "is_active": true}}'
POST .../events with an event name and params object for automations.Contacts power marketing campaigns: you maintain clean lists, consent, and attributes here; campaign authoring and scheduling are product features documented in Campaigns.
| Mistake | Fix |
|---|---|
| Hitting rate limits with one-by-one creates | Use /contacts/imports for bulk loads (respect 50k per request) and backoff |
| Treating marketing contacts as sending suppressions | Use Suppressions for blocked recipients on send streams |