Notifly

Read asynchronously pre-aggregated campaign statistics. Input boundaries are UTC and statistics use UTC hourly buckets: use YYYY-MM-DD with [start, end); equal bounds select no data. Returned stats daily date labels and lastCollectedAt, when present, are KST. If lastCollectedAt is omitted, no freshness value is available. No unavailable reason is returned, so zero or empty results cannot distinguish no activity from aggregation lag.

Check whether a specific user is/was eligible for a specific campaign, with privacy-preserving evidence of why they were or were not targeted. Use this FIRST for any single-user-single-campaign question like "why was this user (not) sent this campaign?" or "is this user in the target?".

Get one saved HTML email template with its complete content for explicit inspection. Campaign and journey creation need only the template_name from list_email_templates; the API loads the content before saving.

Get one latest-editor popup template with its campaign authoring snapshot for in-app-message or in-web-message. Check the returned channel matches the campaign channel, then copy campaign_message into standard message or experiment messages[].message. App/web modal_properties differ: copy them unchanged, including nested key casing; never cross-use channels or recursively camelize them. template_id alone cannot create a popup campaign. Returns the rendered content URL and derived modal properties, but not raw editor state or inline HTML.

Read a Notifly product. The response includes its billing plan and projects accessible through that product.

Read one Notifly project. Use list_projects or get_product first when you need to discover project IDs.

Get project-level channel availability and recent message activity summary from precomputed project statistics.

Read one saved user segment by segment_id.

Get all registered sender profiles for project_id and channel before creating campaigns or user journeys. Returns public sender values, verification/platform support and exact insertion paths; never provider credentials or templates. text-message covers SMS/LMS/MMS and Kakao failover.

Aggregate asynchronously pre-aggregated campaign and user-journey statistics over KST calendar dates. Use YYYY-MM-DD with inclusive [start, end]; equal bounds select one day. KST today is not allowed. No freshness timestamp or unavailable reason is returned. Tags limit results to matching campaigns.

Read one user journey (multi-step scenario) by user_journey_id. Editable configuration fields use the snake_case create/replace contract; stored node IDs remain unchanged. HTML email template content is omitted. Use directly when the ID is known. Do not confuse journeys with campaigns: if the user is asking about a campaign, use the campaign tools instead.

Resolve a public user identifier into a canonical Notifly user reference.

List privacy-preserving delivery records for a campaign and Notifly user.

List the A/B-test variants (branches) of a campaign, including each variant's content and split ratio. Call this WHENEVER a campaign is an A/B test and the user asks about variant content, the split, or a per-variant comparison. Pair with get_campaign_statistics for per-variant performance.

List campaigns in a Notifly project to DISCOVER campaigns or resolve a campaign name to its ID. A campaign is a single-shot or triggered message, distinct from a user journey (a multi-step scenario). Use this ONLY when you do not already know the campaign_id (e.g. the user gave a name, or wants to browse). If you already have the campaign_id, call get_campaign directly — do not list first. Do not call this when the question does not actually require looking at campaign data.

List saved HTML email template names and last modification times for one Notifly project, newest first. Returns no HTML content. Follow next_cursor for more results; use get_email_template to read one template.

List Kakao Alimtalk or Brand Message templates for one project-owned sender. First choose platform and sender_channel_id with get_sender_info. Returns references, creation-compatible type, status and parameter names. Direct Brand Message also returns inline_template: copy it unchanged to message.template (journey: nodes[].message.template) and supply template_parameters from parameter_names. No sender keys or raw provider payloads. Follow next_cursor even on an empty page. Popup templates are separate.

List saved latest-editor popup template metadata for one Notifly project and popup channel. Returns metadata only; it does not expose editor state, rendered HTML, message content, content URLs, or legacy S3-only templates.

List Notifly products accessible to the request credentials. Each entry includes the projects accessible through that product. Use this when you need to discover product or project IDs before calling other tools.

List project-level configured channels for a Notifly project.

List event parameter key presence counts for one project event from precomputed project statistics. Returns keys only, not parameter values or cardinality.

List project event catalog entries available in a Notifly project.

List Notifly projects accessible to the request credentials. The list is bounded by the products the principal can access.

List saved user segments in a Notifly project.

List privacy-preserving channel state for a Notifly user.

List privacy-preserving event summaries for a Notifly user.

Read one user journey's asynchronously pre-aggregated UTC hourly buckets. Use YYYY-MM-DD_HH with [from, to); equal bounds select no buckets. In returned rows, collected_from and collected_to are UTC hour keys, and updated_at is a UTC ISO timestamp; use them as freshness references. Empty statistics has no row-level freshness value. No unavailable reason is returned, so zero or empty results cannot distinguish no activity from aggregation lag.

List user journey sessions for a Notifly user.

List user journeys (multi-step automated scenarios) in a project to DISCOVER journeys or resolve a journey name to its ID. A user journey is distinct from a campaign (a single-shot/triggered message) — only use the journey tools when the subject is a user journey / 시나리오 / 저니. Use ONLY when you do not already know the user_journey_id; if you have it, call get_user_journey directly.

List user property names collected for a Notifly project.

Replace an existing draft campaign in a Notifly project using PUT-style full replacement semantics. ALWAYS call get_campaign first, copy only fields accepted by this tool, keep the returned snake_case names for timing, segment, and message, and preserve fields that are not changing. For CSV targeting, uploaded_filename is the transformed S3 object filename and original_filename is the user-uploaded filename; preserve or replace both together and never guess or change only one. MCP cannot upload a new CSV, so use the Notifly console when the target file must change. The campaign_id path/tool field is the resource identity; do not include id, status, created_at, or updated_at in the payload. Only draft campaigns can be replaced; non-draft campaigns return CONFLICT.

Replace the name and condition definition of a saved user segment.

Replace an inactive user journey draft as a full graph. MANDATORY: first call describe_user_journey_payload(operation="replace") and describe_user_journey_node_payload(operation="replace") for every selected node type/channel/delay_type, then get_user_journey. Copy editable fields from get_user_journey using its snake_case create/replace names; omit response metadata. Existing nodes must use their persisted id; newly added nodes must use a request-local ref. Each graph connection must use exactly one of the matching *_node_id or *_node_ref fields. Refs are resolved during the request and are not persisted as node IDs. This operation is non-activating and preserves the existing REST replacement semantics.