Customer.io API

Retrieve suppression status and reason for an email. Use this tool to find out if an email address has been suppressed by the email service provider (ESP) and the reasons for its suppression.

Create a manual segment with name and description. Use this tool to create an empty manual segment by specifying its name and description. Ideal for organizing contacts or data into new categories. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Create a new data collection in Customerio. Use this tool to create a new collection in Customerio by either providing direct data or a URL for downloading CSV or JSON data. Ensure the collection does not exceed 10 MB, and individual rows are under 10 KB. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Create a new webhook configuration for reporting. Use this tool to set up a new webhook configuration within the Customerio service for reporting purposes. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Delete a collection and its contents. Use this tool to remove a collection and all its contents from the system. Ensure the collection is not referenced in active campaign messages or broadcasts to avoid disrupting communication.

Delete a specified manual segment by ID. Use this tool to delete a specific manual segment in Customerio by providing the segment ID. It's useful for removing outdated or unwanted segments.

Delete an individual newsletter and its associated data. Use this tool to delete a specific newsletter, including its content, settings, and metrics. It will be removed from segments, and its templates will be erased from the Message Library. Additionally, any undelivered in-app messages will be canceled.

Delete a reporting webhook's configuration. Use this tool to remove the configuration of a specific reporting webhook by its ID. Call this when a webhook is no longer needed and should be deleted from the setup.

Retrieve a temporary signed link to download an export. Use this tool to get a signed link for downloading an export from Customerio. The link is only valid for 15 minutes, so it should be used promptly.

Export customer data based on specified filters. Use this tool to export customer data by providing filters and attributes. It returns metadata useful for initiating the data download process. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Initiates export of delivery data for newsletters and campaigns. This tool is used to start an export of delivery data for newsletters, campaigns, or actions based on given filters. Data spans a specified time range, with default and maximum limits. Use it to obtain delivery insights over a specified timeframe. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Retrieve a list of message deliveries and their metrics. This tool retrieves a list of message deliveries, including metrics, within a specified time range in your workspace. Use it to analyze message performance over the most recent six months or a defined period. If no specific time range is provided, it defaults to the last six months.

Filter and search for people in your workspace. Use this tool to filter people by segment ID and attribute values using complex filters such as `and`, `or`, and `not`. The tool returns arrays of `identifiers` with detailed information and `ids` with only ID values. Suitable for retrieving up to 1000 people per request. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Identify campaigns and newsletters using a segment. This tool identifies which campaigns and newsletters are utilizing a specified segment in Customerio. It should be called when you need to determine the dependencies of a segment within your marketing strategies.

Retrieve email addresses suppressed for specific reasons. Use this tool to identify and retrieve email addresses suppressed by the Email Service Provider for reasons such as bounces, blocks, spam reports, or invalid addresses. Supports pagination for large datasets.

Find objects in your workspace using filter conditions. This tool is used to find and return a list of object IDs based on specified filter conditions in your Customerio workspace. It allows paging through results and setting limits on the number of objects returned. Useful for locating, creating, or modifying objects based on specific criteria. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Retrieve IP addresses to allowlist for secure access. Use this tool to obtain a list of IP addresses that should be allowlisted when configuring firewall settings or using a custom SMTP provider's IP management to deny unknown IPs. This is applicable to all message types and webhooks, except push notifications.

Retrieve a list of all segments for your account. Call this tool to get a list of all segments associated with your Customerio account. Use it to fetch and review segment data.

Retrieve an archived copy of a message delivery. Fetches the archived version of a delivery from Customerio, providing details like the message body, recipient, and associated metrics. Limited to 100 requests per day.

Retrieve details of a specific broadcast action. Call this tool to obtain detailed information about a specific action within a broadcast by providing the broadcast and action IDs.

Retrieve link click metrics for a specific broadcast action. This tool retrieves link click metrics for an individual broadcast action. It provides data for a maximum of 45 days, unless specified otherwise. Use appropriate period and step parameters for custom data ranges.

Retrieve metrics for a broadcast action over time steps. Get metrics for an individual broadcast action, both in total and divided by time steps like days or weeks, over a specified period.

Retrieve actions from a specific broadcast. Use this tool to get detailed actions that occur as part of a specific broadcast by providing the broadcast ID.

Retrieve details of broadcast validation errors. This tool helps identify and understand validation errors in broadcast campaigns, focusing on issues within the broadcast audience and associated elements. Use it to diagnose and resolve broadcast errors.

Retrieve metrics for link clicks in a broadcast. This tool returns metrics for link clicks within a specified broadcast, providing both total counts and series data over defined periods such as days or weeks. Useful for analyzing broadcast performance.

Retrieve details about broadcast message deliveries. This tool returns information about message deliveries from an API-triggered broadcast. Use it to get insights on individual deliveries within a specific time range by providing `start_ts` and `end_ts`. If not specified, data for one month post-trigger is returned. The information reflects when the deliveries were created, with a possible delay to actual send time.

Retrieve metadata for a specific broadcast. Use this tool to get detailed metadata for an individual broadcast based on its unique identifier. Useful for tracking and analyzing individual broadcast details.

Retrieve metrics for a specific broadcast over defined time steps. This tool retrieves a list of performance metrics for an individual broadcast, broken down into specified time intervals (steps) such as days or weeks. It is useful for analyzing broadcast performance trends. The metrics are returned from the oldest to the newest period.

Retrieve the status of a broadcast using its trigger ID. Use this tool to get the current status of a broadcast after it has been triggered. Requires the `broadcast_id` and `trigger_id` to fetch the specific status.

Retrieve translation info for a broadcast message. Use this tool to get details about a specific translation of a message within a broadcast by providing the `action_id`. Useful for checking how a message is translated into a specific language.

Retrieve triggers for a specific broadcast. Use this tool to get a list of triggers associated with a particular broadcast in the Customerio service. Useful for understanding the actions set for a broadcast.

Retrieve details for a specific action in a campaign. Use this tool to get detailed information about a specific action within a marketing campaign. It should be called when you need to understand the specifics of campaign actions such as type, status, or execution details.

Retrieve link click metrics for a specific campaign action. This tool retrieves link click metrics for an individual action within a specific campaign. It provides click data for up to 45 days unless specified otherwise and requires at least two steps for any period. Use this tool to analyze link engagement in marketing campaigns.

Retrieve metrics for a specific campaign action. Fetch detailed metrics for an individual action within a campaign. Utilizes version 2, allowing for flexible time ranges and resolution-based metrics. Essential for tracking the performance of campaign actions over time.

Retrieve journey metrics for a specific campaign. This tool retrieves a list of journey metrics for a specified campaign. It provides insights into how many people triggered the campaign and other related metrics within a specified time period and resolution. Useful for campaign performance analysis.

Get link click metrics for a campaign over specified periods. This tool fetches metrics for link clicks within a specified campaign, providing both total and period-specific data (like days or weeks). It's useful for analyzing campaign performance over time.

Retrieve a list of marketing campaigns. Use this tool to get a list of your marketing campaigns and their associated metadata. Ideal for reviewing, auditing, or managing your email campaigns.

Retrieve message deliveries from a campaign. Fetch information on individual message deliveries from a specific campaign over a specified time range. Use parameters like `start_ts` and `end_ts` to refine the data to a specific period.

Retrieve metadata for a specific campaign. Use this tool to get detailed metadata about an individual campaign by specifying the campaign ID.

Fetch metrics for an individual campaign. Use this tool to retrieve a list of metrics for a specific campaign. It supports flexible time-based metrics by utilizing parameters like resolution, time zone, start, and end times. The recommended version 2 provides greater flexibility with these options. This tool is ideal for analyzing campaign performance over time.

Retrieve recent activities for a customer. This tool returns a list of activities performed by or for a specified customer, such as attribute changes and message sends. It provides activity history from the past 30 days, with potential inclusion of older data.

Retrieve attributes and devices for specified customers by ID. Use this tool to get detailed attributes and devices information for up to 100 customers by their IDs. If a provided ID does not exist, it will be omitted in the response. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Retrieve a customer's profile attributes. This tool fetches a list of attributes for a specified customer profile. Useful for creating segments or using in message templates.

Retrieve segments of a specific customer from Customerio. Use this tool to get a list of segments that a specified customer profile is a part of. This can be useful for understanding customer categorization and targeting within the Customerio platform.

Retrieve metrics and details for a specific message delivery. Call this tool to get information and delivery metrics for a specific instance of a message intended for an individual recipient.

Returns information about a specific export from Customerio. Use this tool to fetch details about a particular export by providing the export ID. It retrieves comprehensive information related to the specified export.

Retrieve the status of an import operation. Use this tool to get information on the status and results of a CSV file import operation, including the success of the row imports.

Retrieve metrics for link clicks in a newsletter. This tool fetches metrics for link clicks within a newsletter, providing both total counts and series data over specified periods (e.g., days, weeks). Useful for analyzing newsletter performance over time.

Retrieve delivery info for messages sent from a newsletter. Use this tool to get information about individual message deliveries from a specific newsletter. You can specify a time range using `start_ts` and `end_ts`, otherwise, it defaults to a 6-month period from the first delivery. For longer ranges, up to 12 months of data will be returned from the most recent delivery. Timestamps indicate delivery creation, not the actual send time.

Retrieve metrics for a specific newsletter over time. This tool retrieves a list of metrics for an individual newsletter over specified time intervals, such as days or weeks, presented from oldest to newest. It is useful to analyze the performance of newsletters over time, requiring at least two time steps for valid data retrieval.

Retrieve a list of newsletters and their metadata. Use this tool to obtain a comprehensive list of newsletters along with detailed metadata. Ideal for managing or reviewing newsletter information.

Retrieve test group details for a specific newsletter. Use this tool to obtain information about each test group within a specific newsletter, including content IDs for each group. Ideal for analyzing or verifying test group configurations in newsletters.

Get link click metrics for a newsletter variant. Retrieve metrics related to link clicks for an individual newsletter variant, such as language variations or A/B test messages. By default, the data covers up to 45 days. Specify the period and steps to customize the data range.

Retrieve variant details of a specific newsletter. Use this tool to obtain details about a specific variant of a newsletter, which could represent a language option or part of an A/B test.

Fetch metrics for a specific newsletter variant. This tool retrieves metrics for an individual newsletter variant, such as a language variation or A/B test version. It provides total metrics and stepped metrics over a specified time period, which are arranged chronologically. It requires at least two steps to retrieve data.

Fetch content variants for a specified newsletter. Use this tool to retrieve different content variants of a newsletter, useful for accessing multi-language versions or A/B test variations.

Get information on a newsletter's language variant. Use this tool to obtain details about a particular language variant of a newsletter. Ideal for retrieving specific translations of newsletter content.

Retrieve a list of attributes for a specific object. Use this tool to get attributes of an object, such as account name, billing date, etc., by specifying the object type and ID.

Retrieve a list of object types and their IDs. Use this tool to obtain a list of all available object types in your system along with their incrementing IDs. This is useful when you need to query, create, or modify specific object types by their ID.

Retrieve a list of people matching an email address. Use this tool to find people in your workspace based on their email address. It returns a list of individuals matching the specified email.

Retrieve a list of objects a person is related to. Use this tool to obtain a list of relationships associated with a specific person. It supports pagination for retrieving results in multiple pages. Note that duplicates may appear across pages.

Retrieve people related to a specified object. Use this tool to get a list of people related to a specific object by providing the object type and object ID. Useful for exploring object relationships in Customerio.

Retrieve the customer count for a specific segment. Use this tool to obtain the number of customers belonging to a particular segment identified by segment_id. This can help in analyzing segment size and its potential impact.

Retrieve information about a specific segment. This tool retrieves detailed information about a specific segment using its segment ID. It should be called when segment information is needed for analysis or decision-making.

Retrieve customer details from a specific segment. Use this tool to get a list of customer identifiers in a specified segment. It returns identifiers for each person in the segment, providing more comprehensive information than just IDs. Useful for understanding customer segmentation.

Retrieve information about a specific sender by ID. Use this tool to get detailed information for a specific sender using their ID, which is helpful for email management and verification processes.

Retrieve a list of senders from your workspace. This tool retrieves a list of senders in your workspace, representing the identities from which messages are sent. Use this to manage or display sender information.

Retrieve campaigns and newsletters using a specific sender. Use this tool to obtain lists of campaigns and newsletters that utilize a particular sender identity. It provides insights into where a sender is actively used, helping in managing and analyzing sender strategies.

Retrieve a person's subscription preferences. Returns a list of a person's subscription preferences, including headers, topic names, and descriptions. The data is translated if a language is specified in the query.

Retrieve subscription topics from your workspace. Use this tool to get the list of all subscription topics available in your workspace. It will return an empty array if no topics exist.

Retrieve metrics for clicked links in transactional messages. This tool returns metrics for links clicked from a transactional message, including totals and metrics over specified time periods. Useful for analyzing link engagement trends over days, weeks, etc. Cannot request fewer than two periods (e.g., days or weeks).

Retrieve details of a transactional message. Call this tool to get information about an individual transactional message using its ID.

Fetch delivery details for transactional messages. Retrieve information about individual message deliveries from a transactional message. Use optional parameters to specify a time range for the message data, otherwise, data from the last 6 months is returned by default.

Retrieve metrics for a transactional message over time periods. This tool retrieves metrics for a specified transactional message across defined time steps. It is useful for analyzing message performance over days, weeks, etc., from the oldest to the newest period.

Retrieve content variants of a transactional message. This tool is used to obtain the different language variants of a transactional message's content. It should be called when you need to access the available language or format options for a specific message.

Fetch translation details of a transactional message. Use this tool to obtain details about a translation of a specific transactional message, including its content. It's useful when you need to access different language variants of transactional messages.

Get detailed information about a specific webhook. This tool retrieves information about a specific reporting webhook from Customerio. It should be called when you need details about a particular webhook identified by its webhook ID.

Retrieve a list of API-triggered broadcasts with metadata. Use this tool to get detailed information on all your API-triggered broadcasts, including their metadata. Ideal for keeping track of broadcast activities or managing campaigns.

Retrieve operations in a campaign workflow. This tool retrieves the actions or 'tiles' in a campaign workflow, returning up to 10 actions per call. If more pages of results are available, a 'next' string is included, which can be used to access subsequent pages. Ideal for analyzing or modifying campaign workflows.

Retrieve a list of all collections including names and schemas. Use this tool to obtain all existing collections, providing both their names and schemas. Useful for managing database structures or viewing collection configurations.

Retrieve a list of exports for people or campaign metrics. This tool is used to obtain a list of exports, which are point-in-time records of people or campaign metrics. Call this tool when you need detailed information about exports from Customerio.

Retrieve recent activity logs from the past 30 days. This tool calls the Customerio API to obtain a list of recent activities for people. It returns activity history within the past 30 days, similar to workspace's Activity Logs, and might include older activities.

Retrieve a list of reporting webhooks. Use this tool to get a list of all reporting webhooks configured in your Customerio account. It should be called when you need to access or manage existing reporting webhooks.

Retrieve a list of reusable content snippets from your workspace. Use this tool to obtain snippets, such as common footers, which are reusable content pieces in your workspace.

Retrieve your list of transactional message IDs. This tool retrieves a list of your transactional message IDs used for triggering individual deliveries. It does not include delivery instances themselves.

Retrieve a list of workspaces in your account. Use this tool to get information about all workspaces available in your Customerio account. It provides a list that can be used to view or manage workspaces.

Remove an email address from the suppression list. Use this tool to remove a specific email address from the email service provider's suppression list, allowing future communications to be sent to it.

Removes an unused snippet from the system. This tool removes a snippet that is not in use. If the snippet is currently in use, an error will be returned.

Replace the entire contents of a data collection. Use this tool to completely replace the existing contents of a data collection by specifying the new keys and values. Ideal for cases where a full update is required. Keep in mind the size limitations: collections must not exceed 10 MB and no single row more than 10 KB. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Retrieve contents of a specified collection. Use this tool to fetch the data stored in a specific collection on the Customerio platform. It returns each row as a JSON object, ideal for accessing stored information quickly.

Retrieve details about a specific collection. This tool retrieves information about a collection, including its schema and name, without including the content of the collection. It should be used when you need information about the structure and title of a collection.

Retrieve deliveries sent to a customer within a time range. Use parameters to specify the time range for the messages you want to retrieve. If no time range is provided, it defaults to the most recent 6 months. The tool returns data on when deliveries were created, which may differ from when they were sent.

Get info on a newsletter's language variant in A/B test. Use this tool to obtain details about a specific language variant of a newsletter that is part of an A/B test. It requires the newsletter ID, test group ID, and language code.

Retrieve metadata for an individual newsletter. Call this tool to get detailed information about a specific newsletter using its ID.

Send a customizable transactional email. Use this tool to send a transactional email using Customerio. You can utilize a `transactional_message_id` to specify a template or customize the email by providing `body`, `subject`, and `from` values. If a metrics association is needed, include the `transactional_message_id`. It's designed for sending personalized messages while tracking delivery metrics effectively. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Send a customized transactional push notification. This tool sends a transactional push notification using a specified message template from Customerio. You can override template values at send time using the `transactional_message_id`, which can be the numerical ID or the Trigger Name. Use this tool to send personalized push messages to users. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Send a transactional SMS message using a template. Send a transactional SMS by providing a `transactional_message_id`, which can be the numerical ID or *Trigger Name* of your message template. This allows you to automate SMS communications using predefined templates. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Suppress an email address at the email service provider. Use this tool to suppress an email address at the email service provider (ESP). It ensures that the email address will no longer receive emails through the ESP, while allowing the contact to remain in your Customer.io workspace.

Fetches a translated message for a specific campaign action. Returns a translated version of a message in a campaign using the action ID and specified language. Use when a translated version of a campaign message is needed.

Trigger a broadcast to a specific audience using Customerio. This tool triggers a broadcast campaign in Customerio, allowing for message personalization via provided data. It should be called when you need to send messages to an audience already in your workspace, specified by a segment, email list, customer ID list, user map, or data file. It's important to handle existing users only, as the tool won't add or identify new users. Set flags to skip over non-existent users if needed. Designed for large audience message dispatch rather than individual interactions. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Update the contents of a broadcast action. Use this tool to update the body of messages or HTTP requests in a broadcast action. It should be called when you need to modify the content associated with a specific broadcast action in Customerio. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Update the translation for a broadcast action. Use this tool to update the translation of a specific broadcast action, including message bodies or HTTP request content. This can be useful when you need to update translations for different languages in your broadcast actions. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Update campaign action details and content. This tool updates the contents of a specific campaign action, allowing modifications to messages and HTTP requests. Use it to edit existing campaign steps. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Update a language variant of a campaign action. Use this tool to update the contents of a language variant for a specific campaign action, including the message body and HTTP requests. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Update collection name or replace its contents in Customerio. Use this tool to update the name or fully replace the contents of a specific collection in Customerio. Be careful when changing the collection name if it's referenced in active campaigns, as it will cause the references to return an empty data set. Ensure the collection size is within 10 MB and individual rows are no more than 10 KB. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Add or update customer attribute metadata in your workspace. Use this tool to add new customer attributes or update existing ones. It helps in managing customer data like names and emails, enhancing data understanding for AI tools, and setting sensitivity levels for premium users. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Update or add new events in the workspace. This tool allows you to update existing events or add new ones in the Customerio workspace. It is useful for managing customer actions and integrating new events. Events must be associated with customers via Pipelines or Track APIs to appear in the Data Index. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Update a newsletter variant's content. Use this tool to update the content of a specific newsletter variant, such as a version in a different language or part of an A/B test. Ideal for modifying the body or detail changes in a newsletter. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Update a newsletter's translation for A/B testing. This tool updates the translation of a specific newsletter variant within an A/B test. It's used when you need to modify the language content for different test groups in newsletter campaigns. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Update a newsletter variant's translation. Use this tool to update the translation for a specific variant of a newsletter. This is applicable when your newsletter does not include A/B tests. For A/B tests, you should use a separate tool. Call this tool when you need to modify the language content of a newsletter variant for a given language. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Update or create a snippet with a unique name. Use this tool to update an existing snippet or create a new one. Pass a unique `name` and corresponding `value`. If the snippet already exists, its value will be updated; otherwise, a new snippet will be created. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.