managing-contacts
Manage Mailtrap Contacts
Marketing teams need reliable contact data for campaigns and automations. This skill guides Mailtrap contact creation, imports, lists, fields, events, and sync workflows.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "managing-contacts" from https://skillstore.io/skills/mailtrap-managing-contacts.md and its manifest at https://skillstore.io/api/skills/mailtrap-managing-contacts/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "managing-contacts". A marketer asks how to import 30,000 opted-in contacts into Mailtrap.
Expected outcome:
The skill recommends the bulk import endpoint, confirms the request stays below the 50,000 contact limit, and includes status polling guidance.
Using "managing-contacts". An engineer asks whether bounced recipients should be removed through contact lists.
Expected outcome:
The skill explains that sending suppressions are separate from marketing contacts and points the engineer to suppression-specific guidance.
Using "managing-contacts". A growth team wants to trigger automations when users log in.
Expected outcome:
The skill suggests using custom contact events with a clear event name and approved parameters for Mailtrap automations.
Security Audit
SafeThe static findings are false positives from Markdown tables, fenced curl examples, and official Mailtrap documentation links. No prompt injection, hidden code execution, path traversal, or unauthorized data exfiltration evidence was found.
Risk Factors
⚡ Contains scripts (2)
⚙️ External commands (18)
🌐 Network access (22)
📁 Filesystem access (2)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/mailtrap-managing-contacts/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/mailtrap-managing-contacts?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/mailtrap-managing-contacts?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/mailtrap-managing-contacts/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/mailtrap-managing-contacts.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
mailtrap. (2026). managing-contacts security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/mailtrap-managing-contacts/audits/4BibTeX citation
@techreport{mailtrap-mailtrap-managing-contacts-2026,
author = {mailtrap},
title = {managing-contacts security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/mailtrap-managing-contacts/audits/4},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "managing-contacts security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
- name: "mailtrap"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/mailtrap-managing-contacts/audits/4"
identifiers:
- type: other
value: "skillstore:mailtrap-managing-contacts:audit:4"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Plan CRM Contact Sync
Map CRM fields to Mailtrap contacts, lists, and custom fields before a scheduled sync.
Prepare Bulk Audience Import
Design a safe bulk import flow that respects Mailtrap limits and import status polling.
Track Contact Automation Events
Define custom event names and payload fields that can support Mailtrap automations.
Try These Prompts
Help me create one Mailtrap marketing contact with email, first name, last name, company, and list membership.
Plan a Mailtrap bulk contact import for these fields, list IDs, and consent rules. Include polling and rate limit guidance.
Map my CRM contact attributes to Mailtrap custom fields and lists. Flag missing fields and risky assumptions.
Review my Mailtrap contact sync and custom event workflow. Check authentication, field names, import limits, and suppression boundaries.
Best Practices
- Check the Mailtrap OpenAPI spec before finalizing field names or request bodies.
- Use bulk imports for large loads and poll import status after submission.
- Keep API tokens in environment variables and avoid sharing real tokens in prompts.
Avoid
- Do not import contacts without consent or list membership rules.
- Do not treat marketing contact filters as sending suppression controls.
- Do not send one request per contact when a bulk import is more appropriate.