Skip to content

Integration · Marketing

symplify.com

Connect Claude & ChatGPT to Symplify

Ask your AI what messages a contact has received, whether they are subscribed, or what they have bought, and get the answer from Symplify. It can update a contact's properties, change subscription status, send events and start a journey for one contact. Customer questions get answered without opening each list by hand.

Connect Symplify free

Free plan, no credit card. Takes about a minute.

Try asking

  • “Which messages has contact 48213 on our newsletter list received?”

    The AI lists the messages sent to that contact on the list.

  • “Is [email protected] still subscribed to the newsletter list?”

    It reads the contact's subscription status on the list, including mobile and audio status.

  • “Show me the purchase history for contact 48213.”

    It lists the contact's purchase history rows from Symplify.

What your AI can do

Contacts

Read a contact on a list with its properties, see the messages sent to it and its purchase history, and update its properties.

Subscriptions

Check and change a contact's subscription status on a list for email, mobile and audio, or remove the contact from a list.

Journeys and events

List and read journeys, start a journey for one contact, and send events that can trigger journeys and messages.

  • “Update the email address for contact 48213 on the customer list.”

    It updates the contact's emailAddress property on that list and leaves other properties unchanged.

  • “Start the welcome journey for contact 48213.”

    It finds the journey and starts it for the contact. The journey may send messages to them.

  • “Which contact properties do we have, and what type are they?”

    It lists the properties defined in your account with their names and data types.

78 tools for Symplify

These tools are switched on when you connect. You can switch any of them off, or require your approval before it runs.

  • create_contactChanges dataCreate a new contact. Required: body.
  • create_customChanges dataCreate a new custom. API summary: Start export.
  • create_documenttypeChanges dataCreate a new documenttype. API summary: Create document type.
  • create_dryrunChanges dataCreate a new dryrun. Required: body. API summary: Start dry run batch.
  • create_fixedChanges dataCreate a new fixed. Required: body. API summary: Start batch campaign generation.
  • create_fixed_recipientChanges dataCreate a new recipient for a fixed. API summary: Specify campaign recipients.
  • create_importChanges dataCreate a new import. API summary: PH import file - start job.
  • create_import_dataChanges dataCreate a new data for a import. API summary: PH import - upload file.
  • create_list_importChanges dataCreate a new import for a list. API summary: Start Import.
  • create_propertyChanges dataCreate a new property. API summary: Create property.
  • create_rootChanges dataCreate a new root. API summary: BATCH NOTIFICATION.
  • create_rowChanges dataCreate a new row. API summary: PH import JSON rows.
  • create_scheduleChanges dataCreate a new schedule. API summary: Create scheduled anonymization.
  • create_snippetChanges dataCreate a new snippet. API summary: Create snippet.
  • create_v2Changes dataCreate a new v2. Required: body. API summary: Start import.
  • delete_contact_documentDeletesPermanently delete a document by document type id. Destructive action; may require approval. API summary: Delete all docs in specific DocType for a contact.
  • delete_contact_documentsMoves moneyPermanently delete a document by original id. Financial or irreversible action; may require approval. API summary: Delete all docs for a contact.
  • delete_datadocDeletesPermanently delete a datadoc by datadoc id. Destructive action; may require approval. API summary: Delete single doc by doc id.
  • delete_document_externalidDeletesPermanently delete a externalid by externalid. Destructive action; may require approval. API summary: Delete single doc in specific DocType by externalId.
  • delete_documenttypeDeletesPermanently delete a documenttype by document type id. Destructive action; may require approval. API summary: Delete document type.
  • delete_propertyDeletesPermanently delete a property by property id. Destructive action; may require approval. API summary: Delete property.
  • delete_scheduleDeletesPermanently delete a schedule by anonymization id. Destructive action; may require approval. API summary: Delete scheduled anonymization.
  • delete_snippetDeletesPermanently delete a snippet by snippet id. Destructive action; may require approval. API summary: Delete snippet.
  • delete_webhookDeletesPermanently delete a webhook by event type id. Destructive action; may require approval. API summary: Remove webhook.
  • export_batchesChanges dataExport batches. API summary: Start export.
  • get_batchGet one batch by batch id. API summary: Get Batch info.
  • get_batch_getGet one batch by dry run id. API summary: Check Dry Run status.
  • get_contactGet one contact on a list by `list_id` and the contact's `original_id`, with its properties.
  • get_contact_documentGet one document for a contact by documenttypeid. API summary: Get all docs in a type for a contact.
  • get_contact_subscription_statusGet a contact's subscription status on a list by `list_id` and `original_id`. `body` is not used; pass {}.
  • get_datadocGet one datadoc by datadoc id. API summary: Get specific doc by doc id.
  • get_document_externalidGet one externalid for a document by externalid. API summary: Get single doc in specific DocType by externalId.
  • get_documenttypeGet one documenttype by document type id. API summary: Get document type by id.
  • get_dry_run_resultList results for a batch. API summary: Get Dry Run result.
  • get_filterGet one filter by filter id. API summary: Get segment JSON.
  • get_fixedGet one fixed by campaign generation id. API summary: Generation info.
  • get_futureGet one future by batch progress token. API summary: Import status.
  • get_journeyGet one journey by `journey_id`. `body` is not used; pass {}.
  • get_scheduleGet one schedule by anonymization id. API summary: Scheduled anonymization by id.
  • get_snippetGet one snippet by snippet id. API summary: Snippet by Id.
  • get_webhookGet one webhook by event type.
  • list_batch_resultsList results for a batch. API summary: Batch result.
  • list_columnsList columns. API summary: Get PH column mapping.
  • list_contact_documentsList documents for a contact. API summary: Get all docs for a contact.
  • list_contact_messagesList the messages sent to a contact on a list, by `list_id` and `original_id`. `body` is not used; pass {}.
  • list_contact_purchase_historyList a contact's purchase history rows, by `list_id` and `original_id`.
  • list_datadoc_historiesList histories for a datadoc. API summary: Get specific doc history by doc id.
  • list_documenttypesList documenttypes. API summary: Get all document types.
  • list_journey_overviewsList overviews for a journey. API summary: Specific Journey overview.
  • list_journeysList all journeys (automated communication flows). `body` is not used; pass {}.
  • list_overviewsList overviews. API summary: All Journeys overviews.
  • list_propertiesList the contact properties (fields) defined in the account, with names and data types.
  • list_schedulesList schedules. API summary: All scheduled anonymizations.
  • list_snippetsList snippets. API summary: All snippets.
  • list_tempblocksList tempblocks. API summary: Temporary block contact.
  • list_version_stepsList steps for a version. API summary: Journey steps by versions.
  • list_webhooksList webhooks. API summary: All webhooks.
  • remove_contact_from_listDeletesRemove a contact from a list by `list_id` and `original_id`. This cannot be undone. `body` is not used; pass {}.
  • send_eventChanges dataSend an event for a contact (`contact_id`) with an event `type` and `properties`. Events can trigger journeys and messages.
  • set_contact_subscription_statusVisible to othersChange a contact's subscription status on a list by `list_id` and `original_id`, using `status`, `mobile_status` or `audio_status`. This controls whether they receive messages.
  • start_journey_for_contactChanges dataStart a journey for one contact by `journey_id` and the contact's `original_id`, optionally passing contact `properties` (name, email, mobile) and `save_props`. The journey may send messages to the contact.
  • update_anonymizationsVisible to othersUpdate an existing anonymization identified by customer id. Has effects visible outside this system. API summary: Anonymize contact.
  • update_app_devicesVisible to othersUpdate an existing device identified by appid. Has effects visible outside this system. API summary: Register device token.
  • update_columnsVisible to othersUpdate an existing column identified by customer id. Has effects visible outside this system. API summary: Set PH column mapping.
  • update_contactChanges dataUpdate a contact's properties (e.g. emailAddress and custom attributes in `properties`) on a list, by `list_id` and `original_id`.
  • update_contact_2Changes dataUpdate an existing contact identified by upload url. API summary: Upload file.
  • update_documentChanges dataUpdate an existing document identified by upload url. API summary: Upload file.
  • update_documenttypeChanges dataUpdate an existing documenttype identified by document type id. API summary: Update document type.
  • update_fortypeChanges dataUpdate an existing fortype identified by doc type id. API summary: Upsert doc.
  • update_invalidationsVisible to othersUpdate an existing invalidation identified by appid. Has effects visible outside this system. API summary: Invalidate device token.
  • update_journeyChanges dataUpdate an existing journey identified by journey id. API summary: Update Journey.
  • update_list_recipientChanges dataUpdate an existing recipient identified by import id. API summary: Upload contacts.
  • update_propertyChanges dataUpdate an existing property identified by property id. API summary: Update property.
  • update_purgeChanges dataUpdate an existing purge identified by document type id. API summary: Delete all documents in a DocType.
  • update_scheduleChanges dataUpdate an existing schedule identified by anonymization id. API summary: Update scheduled anonymization.
  • update_snippetChanges dataUpdate an existing snippet identified by snippet id. API summary: Update snippet.
  • update_tempblocksVisible to othersUpdate an existing tempblock identified by customer id. Has effects visible outside this system. API summary: Set temporary block for contact.
  • update_webhooksMoves moneyUpdate an existing webhook identified by customer id. Financial or irreversible action; may require approval. API summary: Set webhook URL.

Set up in three steps

  1. 1

    Pick the app

    Create a free HeyMyApps account and choose Symplify from the app list.

  2. 2

    Paste your key

    Paste three values: your Symplify server number, your API token and your customer ID. In Symplify open Account settings > Symplify API to find the API token and the server number, which is the x in eu-proxy-x.symplifymail.com (for example 2 in eu-proxy-2.symplifymail.com). Your customer ID is shown at the bottom of Symplify's main menu.

  3. 3

    Add the link to your AI

    You get a personal MCP link. Add it to Claude, ChatGPT or Cursor:

    1. Click your name, then Settings › Connectors › Add custom connector.
    2. Paste your link as the Remote MCP server URL.
    3. Switch it on from the + menu in a chat.

Questions

What can the AI do in Symplify?

The AI can read contacts on a list, their properties, sent messages, purchase history and subscription status, and list journeys and contact properties. It can update contact properties, change subscription status, remove a contact from a list, send events and start a journey for a contact.

Does the AI see my Symplify API token?

No. Your Symplify API token and account details are encrypted at rest and never shown to the AI. After you save them, they are not shown again, not even to you. The AI only sees the results of the tools it calls.

Can I control what the AI is allowed to do?

Yes. You choose which tools are switched on, so you can start with lookups only. Starting a journey or sending an event can send messages to a contact, changing subscription status controls whether they get messages, and removing a contact from a list cannot be undone. These can require your approval before they run. Every tool call is logged.

Does it work with ChatGPT?

Yes. In ChatGPT go to Settings › Apps & Connectors › Advanced and turn on Developer mode, then add your HeyMyApps link. Developer mode needs a paid ChatGPT plan: Plus, Pro, Business or Enterprise. The same link also works in Claude (Settings › Connectors › Add custom connector), Cursor and other MCP clients.

What does it cost?

HeyMyApps has a free plan with no credit card required. Paid plans bill per completed task. You also need your own Symplify account.

Why does Symplify need a server number and customer ID?

Symplify accounts run on different servers, named like eu-proxy-2.symplifymail.com, so HeyMyApps needs the number to reach the right one. The customer ID tells Symplify which account the API token belongs to. You find the token and server number under Account settings > Symplify API, and the customer ID at the bottom of the main menu.

Let your AI work in Symplify today.

Start free. Your key stays encrypted, and you decide what the AI may do.

Connect Symplify free

HeyMyApps is not affiliated with Symplify. Product names are trademarks of their owners.