# Mautic integrations: contacts and segments

> Create a contact, create a segment and create a campaign in Mautic, and start a workflow when Mautic sends “Contact created”.

**Canonical page:** https://tray.ai/connectors/mautic-integrations/
**Categories:** Marketing
**Connects through:** HTTP Connector

## Overview

Mautic is open source marketing automation software that teams host themselves to manage contacts, segments, email campaigns, forms and lead scoring. Tray.ai connects to Mautic through the HTTP Connector, so your workflows can call the Mautic API alongside the rest of your stack.

## Use cases

### Contacts

Read, create, update, and delete contacts in Mautic from any Tray.ai workflow. The Mautic API covers calls such as list contacts and create a contact.

- List contacts
- Create a contact
- Edit a contact

### Segments

Read, create, and delete segments in Mautic from any Tray.ai workflow. The Mautic API covers calls such as list segments and create a segment.

- List segments
- Create a segment
- Add contact to segment

### Campaigns

Read, create, and delete campaigns in Mautic from any Tray.ai workflow. The Mautic API covers calls such as list campaigns and create a campaign.

- List campaigns
- Create a campaign
- Add contact to campaign

### Emails

Read and create emails in Mautic from any Tray.ai workflow. The Mautic API covers calls such as list emails and create an email.

- List emails
- Create an email
- Send email to contact

### Companies

Read, create, update, and delete companies in Mautic from any Tray.ai workflow. The Mautic API covers calls such as list companies and create a company.

- List companies
- Create a company
- Edit a company

### Mautic events

Start a Tray.ai workflow the moment something happens in Mautic. Mautic sends events such as contact created and contact updated to a Tray.ai webhook trigger.

- Contact created
- Contact updated
- Contact deleted

## Challenges Tray.ai solves

### Keeping Mautic credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Mautic credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Mautic API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Mautic API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Mautic?

Yes. Tray.ai connects to Mautic through the HTTP Connector, which calls the Mautic API directly. Any call the Mautic API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Mautic?

The Mautic API uses OAuth 2.0 and basic authentication. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Mautic connector?

Mautic runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Mautic connector from the Mautic API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/