marketing_automation
iPost
Connect iPost to Elaichi and hand every teammate a governed MCP endpoint — 38 tools ready to call from Claude, Cursor, or any MCP client, clamped by roles, restrictions, and an audit log.
AI tools
iPost tools for your AI agents
38 tools are ready to mint as an MCP endpoint the moment you connect iPost — governed by the same roles, restrictions, and audit log as everything else in Elaichi.
create_a_ipost_contact
Add a contact to the iPost account. GlobalEmailStatus and GlobalMobileStatus are assumed true when their corresponding Email or Mobile fields are present, and ignored when those fields are absent. Returns: Contact_ID, Email, Mobile, GlobalEmailStatus, GlobalMobileStatus.
update_a_ipost_contact_by_id
Update an iPost contact's information by ContactID. GlobalEmailStatus and GlobalMobileStatus are assumed true when their corresponding Email or Mobile fields are present, and ignored when those fields are absent. Returns: Contact_ID, Email, Mobile, GlobalEmailStatus, GlobalMobileStatus. Required: id.
get_single_ipost_contact_by_id
Retrieve an iPost contact using the blob — an encrypted tracking token optionally appended to tracked links in iPost mailings. Returns: Contact_ID, Email, Mobile, GlobalEmailStatus, GlobalMobileStatus. Required: id (blob value).
list_all_ipost_contacts
List contacts on a specific iPost list by list ID. Returns up to 10,000 contact records per call. Returns: Contact_ID, Email, Mobile, GlobalEmailStatus, GlobalMobileStatus. Required: list_id.
ipost_contacts_bulk_create
Add multiple contacts to an iPost journey automation. Each recipient can be identified by an existing Contact_ID or by Email (which may create a new contact if no match is found). An optional Properties object supplies iTL template variable values for journey email assembly, overriding matching contact profile fields. Returns an opaque confirmation response from the journey automation endpoint. Required: journey_id, Recipients.
get_single_ipost_contact_status_by_id
Get the opt-in/opt-out status of a contact across all static lists and topics in ipost. Returns: lists, topics — each keyed by identifier with a value of true if the contact is opted in or false if opted out. Required: id.
create_a_ipost_list
Create a new list in ipost. Returns: id.
update_a_ipost_list_by_id
Update an existing list in ipost by id. Returns: id. Required: id.
delete_a_ipost_list_by_id
Empty an ipost list by removing all contacts from it. Returns an empty 204 response on success. Required: id.
create_a_ipost_md_5_list_contact
Add one or more contacts to an ipost MD5 Suppression List. Uploaded email addresses are hashed to MD5 format upon ingestion; matching is case-sensitive, so the case of each address must match exactly for suppression to apply. Returns an empty 204 response on success. Required: list_id.
ipost_contact_lists_bulk_create
Add a contact in ipost to one or more lists. Returns an empty 204 response on success. Required: contact_id. Note: GlobalEmailStatus and GlobalMobileStatus are assumed true when absent if the corresponding Email or Mobile fields are present, and are ignored when the corresponding fields are absent.
delete_a_ipost_list_contact_by_id
Remove one or more contacts from an iPost list. Required: list_id. Returns an empty 204 response on success.
ipost_list_contacts_bulk_create
Add or update one or more contacts in an iPost list using encrypted blob tokens. Blobs encode contact identity information and can be sourced from iPost email tracking parameters appended to tracked URLs. Required: list_id. Returns an empty 204 response on success.
create_a_ipost_column
Create a new contact column in ipost. Returns: id, name.
delete_a_ipost_column_by_id
Delete an existing contact column in ipost by id. Returns an empty 204 response on success. Required: id.
list_all_ipost_columns
List all existing contact columns in ipost. Returns: id, name.
create_a_ipost_process_automation
Create a new Process Automation in ipost, specifying automation activities and schedule configuration. Returns: id, status. Supports special automation_schedule.schedule_time_zone values: same_time_sending (Recipient Local Time) and send_time_optimisation (Send Time Optimization), in addition to standard timezone identifiers.
update_a_ipost_process_automation_by_id
Update the status of an existing Process Automation in ipost. Returns: id, status. Required: id, status.
delete_a_ipost_process_automation_by_id
Delete a Process Automation from your ipost account by id. Returns an empty 204 response on success. Required: id.
create_a_ipost_journey_automation
Create a Journey Automation in ipost. Supply recipients via the Recipients array (using Contact_ID for existing contacts or Email for new ones, plus optional Properties for iTL variable substitution) and define automation steps via Automation_Activities (use the children array for multi-step flows). Returns: id.
get_single_ipost_journey_automation_by_id
Search for Journey Automations in ipost. Returns matching journey automation records from the data envelope. Returns: id.
update_a_ipost_journey_automation_by_id
Update a Journey Automation in ipost by id. Update enrolled recipients via the Recipients array (Contact_ID, Email, Properties) and redefine automation steps via Automation_Activities (use the children array for multi-step flows). Returns: id. Required: id.
create_a_ipost_journey_automation
Add contacts to an ipost journey automation to enroll them in the journey sequence. Each recipient can be an existing contact identified by Contact_ID, or a new contact identified by Email; an optional Properties object supplies iTL variable substitutions for email content used by the journey. Returns an empty 204 response on success. Required: journey_id.
create_a_ipost_datatable
Create a new DataTable in ipost. Returns the id of the newly created DataTable.
update_a_ipost_datatable_by_id
Modify an existing DataTable in ipost by id. Returns the id of the updated DataTable. Required: id.
list_all_ipost_datatable_records
List records from an ipost DataTable. Returns records including id and attributes (user-defined DataTable column values). Maximum 100 records per call; use the `start` body parameter to set the pagination offset. Required: datatable_id.
ipost_datatable_records_bulk_update
Add or update records in an ipost DataTable. Accepts a JSON body with record data whose fields correspond to the user-defined columns of the specified DataTable. Required: datatable_id.
get_single_ipost_data_table_attribute_by_id
Retrieve all attributes of a specific ipost Data Table by its id. Returns: status, and a data array where each attribute includes data_type, label, key, and required. Required: id.
delete_a_ipost_asset_by_id
Delete an asset in ipost by id. Returns an empty 204 response on success. Required: id.
get_single_ipost_bulk_import_by_id
Get the status of a bulk import in ipost by id. Returns: id, status (one of: 'new', 'inprogress', 'completed', 'error'). Required: id.
create_a_ipost_auth_session
Create an ipost authentication session by submitting credentials. Returns: data (containing token, valid_for, and expires) and status. The token has a fixed validity window and must be re-issued after expiry. Required: client_id, client_secret.
create_a_ipost_contacts_upsert
Add or update a contact record in ipost using the addUpdate endpoint. Returns: contact_id, email, properties. Required: client_token, email.
get_single_ipost_contacts_blob_by_id
Retrieve an iPost contact using the blob, an encrypted token that encodes contact identity and is optionally appended to tracked email links. Returns the contact's email, contact_id, and properties. Required: id.
update_a_ipost_contacts_blob_by_id
Add or update one or more iPost contacts on a list using the blob, an encrypted token that identifies the contact via tracked email links. Returns the contact's email, contact_id, and properties. Required: id.
get_single_ipost_contact_statuses_blob_by_id
Retrieve iPost contact status information for a subscriber identified by their encrypted blob token — an optional URL parameter appended to tracked links that encodes the contact's identity. Returns the contact's identification and subscription status including ContactID, Email, GlobalEmailStatus, and GlobalMobileStatus. Required: client_token, blob.
delete_a_ipost_lists_empty_by_id
Empty an ipost list by removing all contacts from it. Returns an empty 204 response on success. Required: id.
create_a_ipost_process_automations_start
Start a process automation in ipost for the specified automation_id. Initiates the automation only when its status is active; the call returns an error if the automation's status is stopped, draft, or paused. Returns an empty 204 response on success. Required: automation_id.
ipost_contact_lists_blob_bulk_create
Bulk add a contact to one or more iPost lists using the blob token mechanism. Submits a JSON body against the contact identified by id to associate them with lists via blob. Returns an empty 204 response on success. Required: id.
How it works
From iPost account to governed MCP endpoint
Connect
Link a iPost account through Elaichi's hosted connect flow. Credentials are vaulted — nobody, including the AI, ever sees them.
Compose
The connection becomes a toolbox instantly. Curate which iPost tools are exposed, rename them, or freeze arguments.
Mint
Mint a personal MCP endpoint on that toolbox and paste it into Claude, Cursor, or any MCP client — governed by roles, restrictions, and audit logs.
Give every teammate a governed MCP server
Start a 14-day Gold trial — connect a product, curate a toolbox, and paste an endpoint into Claude or Cursor in minutes.