Skip to content

Integration · Marketing

agillic.com

Connect Claude & ChatGPT to Agillic

Ask your AI what Agillic knows about a recipient, which target groups they are in or what you have sent them, and it reads the answer from Agillic. It can create and update recipients, add them to static target groups, trigger events and queue them into flows. Actions that can start emails or SMS can require your approval first.

Connect Agillic free

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

Try asking

  • “What do we have on [email protected]?”

    The AI gets the recipient by email and shows the Person Data fields you ask for.

  • “Which target groups is Jane in?”

    It lists the target groups the recipient belongs to.

  • “What have we sent Jane in the last three months?”

    It reads her communication history for that period: emails, SMS and other messages.

What your AI can do

Recipients and Person Data

Search, get, create and update recipients with your own Person Data fields, and read their one-to-many table rows.

Target groups

List target groups, see which ones a recipient is in, and add or remove recipients in static target groups.

Flows, events and history

Queue recipients into flows, trigger events, list a recipient's events and read what has been sent to them.

  • “Add a new recipient: Lars Holm, [email protected].”

    It checks the Person Data field names, searches for an existing recipient to avoid a duplicate and creates Lars.

  • “Put these 20 emails in the VIP static target group.”

    It adds the recipients to the static target group by name.

  • “Start the welcome flow for [email protected].”

    It queues the recipient into the flow. The flow may then send him emails or SMS.

62 tools for Agillic

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

  • add_recipient_to_flowChanges dataQueue a recipient into a flow by `flow_id` and `recipient_id`. The flow may send them emails or SMS.
  • add_recipients_to_target_groupChanges dataAdd recipients to a static target group: `target_group` (name) and `batch` of recipient identifiers (e.g. emails).
  • create_or_update_a_number_of_recipientsVisible to othersUpdate an existing recipient. Has effects visible outside this system. API summary: Create or update a number of recipients.
  • create_recipientChanges dataCreate a recipient; `person_data` is an object of Person Data field names and values, e.g. {"EMAIL": "[email protected]"}. Search first to avoid duplicates.
  • create_recipient_queue_with_contextChanges dataCreate a new queue with context for a recipient. Required: body. API summary: Queue a flow for a recipient with context.
  • create_table_recordChanges dataCreate a new record for a table. API summary: Creates a Global Data Table record.
  • delete_consentMoves moneyPermanently delete a consent by recipient id. Financial or irreversible action; may require approval. API summary: Withdraw consent.
  • delete_recipientDeletesPermanently delete a recipient and their data by `recipient_id`.
  • delete_recipient_s_one_to_many_recordsVisible to othersUpdate an existing one to many table identified by table id. Has effects visible outside this system. API summary: Delete Recipient's One To Many records.
  • delete_table_recordDeletesPermanently delete a record by record id. Destructive action; may require approval. API summary: Deletes a Global Data Table record.
  • get_globaldatumGet one globaldatum by global data name. API summary: Read Global Data.
  • get_onetomanyGet one onetomany by table id. API summary: Return the metadata for the given one-to-many table.
  • get_recipientGet one recipient by `recipient_id` (any unique Person Data, such as the email), optionally only the `person_data_fields` you need.
  • get_recipient_communication_historyChanges dataGet the messages sent to a recipient between `date_start` and `date_end`, optionally by `communication_type` (email, sms, print, transactionalemail, app_push).
  • get_recipient_eventGet one event for a recipient by event id. API summary: Get specific Event.
  • get_recipient_table_rowsGet a recipient's rows in a one-to-many table by `recipient_id` and `table_id`.
  • get_tableGet one table by table id. API summary: Returns a Global Data Table.
  • get_table_get_global_data_table_metadataGet one table by table id. API summary: Returns a Global Data Table metadata.
  • get_table_limitGet one limit for a table by row num. API summary: Returns a Global Data Table.
  • get_table_recordGet one record for a table by record id. API summary: Returns a Global Data Table record.
  • get_target_groupGet one target group by `targetgroup_id`.
  • get_taskGet one task by task id. API summary: Returns Task status.
  • get_task_get_taskGet one task by task id. API summary: Query the status of a One To Many by task id.
  • get_task_read_pageGet one task by task id. API summary: Read export page.
  • get_task_task_statusGet one task by task id. API summary: Returns Task status.
  • list_one_to_many_tablesList the one-to-many tables (e.g. purchases, bookings) with their IDs.
  • list_person_data_fieldsList the Person Data fields defined in Agillic (e.g. EMAIL, FIRSTNAME). Use these names when creating or updating recipients.
  • list_recipient_eventsList the events available for a recipient by `recipient_id`.
  • list_recipient_one_to_many_tablesList one to many tables for a recipient. API summary: List Recipient's One To Many tables with its content.
  • list_recipient_target_groupsList the target groups a recipient belongs to, by `recipient_id`.
  • list_tablesList tables. API summary: Returns list of Global Data Table defined in the solutions.
  • list_target_groupsList target groups (segments) with their IDs and names.
  • remove_recipients_from_target_groupDeletesRemove recipients from a static target group: `target_group` (name) and `batch` of recipient identifiers.
  • search_globaldataSearch globaldata by filter. Use this to find existing globaldata before creating a new globaldatum. API summary: List Global Data.
  • search_recipientsSearch recipients with a Person Data `filter` (e.g. by EMAIL or NAME). Use to check if a recipient exists.
  • trigger_recipient_eventChanges dataRegister that a recipient achieved an event (`recipient_id`, `event_id`). This can start flows that send them messages.
  • update_consentChanges dataUpdate an existing consent identified by recipient id. API summary: Add consent.
  • update_eventChanges dataUpdate an existing event. API summary: Achieve Event with contextual data.
  • update_feedbackChanges dataUpdate an existing feedback identified by recipient id. API summary: Record device feedback.
  • update_flowChanges dataUpdate an existing flow identified by flow id. API summary: Execute a flow.
  • update_flow_execute_flow_with_contextChanges dataUpdate an existing flow identified by flow id. API summary: Execute a flow with context.
  • update_globaldatumChanges dataUpdate an existing globaldatum identified by global data name. API summary: Update Global Data.
  • update_one_to_many_tableVisible to othersUpdate an existing one to many table. Has effects visible outside this system. API summary: Update Recipient's One To Many records.
  • update_one_to_many_table_async_batch_delete_one_to_many_table_reVisible to othersUpdate an existing one to many table. Has effects visible outside this system. API summary: Delete Recipient's One To Many records.
  • update_one_to_many_table_async_truncate_one_to_many_tableChanges dataUpdate an existing one to many table. API summary: Clear Recipient's One To Many table.
  • update_onetomanyChanges dataUpdate an existing onetomany identified by table id. API summary: Truncates an entire One-To-Many table.
  • update_recipientChanges dataUpdate a recipient by `recipient_id`; `person_data` holds the Person Data fields to change.
  • update_recipient_eventChanges dataUpdate an existing event identified by event id. API summary: Achieve Event with Contextual Data.
  • update_recipient_one_to_many_tableChanges dataUpdate an existing one to many table identified by table id. API summary: Clear Recipient's One To Many table.
  • update_recipient_promotionChanges dataUpdate an existing promotion identified by promotion id. API summary: Get Propositions by Promotion.
  • update_recipient_s_one_to_many_recordsVisible to othersUpdate an existing one to many table identified by table id. Has effects visible outside this system. API summary: Update Recipient's One To Many records.
  • update_registerChanges dataUpdate an existing register identified by recipient id. API summary: Register device.
  • update_tableChanges dataUpdate an existing table identified by table id. API summary: Truncates the Global Data Table.
  • update_table_batch_create_global_data_table_recordsVisible to othersUpdate an existing table identified by table id. Has effects visible outside this system. API summary: Batch create records in a Global Data Table.
  • update_table_batch_delete_global_data_table_recordsVisible to othersUpdate an existing table identified by table id. Has effects visible outside this system. API summary: Batch delete selected records in Global Data Table.
  • update_table_batch_update_global_data_table_recordsVisible to othersUpdate an existing table identified by table id. Has effects visible outside this system. API summary: Batch update records in a Global Data Table.
  • update_table_recordChanges dataUpdate an existing record identified by record id. API summary: Updates a Global Data Table record.
  • update_taskChanges dataUpdate an existing task. API summary: Execute activity export for file type.
  • update_unregisterChanges dataUpdate an existing unregister identified by recipient id. API summary: Unregister device.
  • update_v2Changes dataUpdate an existing v2. API summary: Asynchronous update or insert number of recipients.
  • update_v2_async_combined_recipient_upsertChanges dataUpdate an existing v2. API summary: Asynchronous update or insert a recipient with person data, otm data, and event achievement.
  • update_v2_async_delete_recipientsChanges dataUpdate an existing v2. API summary: Asynchronous batch delete operation.

Set up in three steps

  1. 1

    Pick the app

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

  2. 2

    Paste your key

    Paste the Developer Key and Secret from your Agillic instance. Open Administration > Integrations > API, choose the environment (staging or production), enter a description, pick the scope and click Create new credentials. HeyMyApps uses them to get access tokens, so there is no separate sign-in.

  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 Agillic?

It can search and read recipients, their Person Data, one-to-many table rows, events, target groups and communication history, and list Person Data fields, tables and target groups. It can create, update and delete recipients, add recipients to or remove them from static target groups, trigger events and queue recipients into flows.

Does the AI see my Agillic credentials?

No. Your Agillic credentials 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. Triggering events and adding recipients to flows can start emails or SMS, and deleting a recipient removes their data permanently, so these can require your approval before they run. Every tool call is logged.

Does it work with ChatGPT?

Yes. In ChatGPT, open Settings › Apps & Connectors › Advanced, turn on Developer mode and 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?

Agillic connects with OAuth, and OAuth connections need the HeyMyApps Pro plan or above. HeyMyApps also has a free plan with no credit card, but it does not include this connection. Paid plans bill per completed task. You also need your own Agillic account.

Does the AI send emails from Agillic directly?

No. There is no tool that sends a single email. The AI can add a recipient to a flow or register an event, and your flows in Agillic decide what is sent. That way your own templates and rules stay in control.

Let your AI work in Agillic today.

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

Connect Agillic free

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