Systeme.io

Create an inactive classic course for the authenticated user. Read describe_courses before starting to build the course. Use get_domains with workableOnly=true and get_course_themes to obtain valid domainId and themeId. Ask for the course name and path when they are not provided. The path must use only lowercase letters, numbers, hyphens, and underscores. After a successful call, show the user the course management link from courseEditUrl.

create_classic_course

Create a lecture with an empty page in a classic membership course module. Lectures are appended; within one module, await each creation before creating the next lecture, never create them in parallel. Check each returned position against the intended order. Set active to true only when creating a new course that is still inactive. For an existing course, leave the lecture inactive, save and verify its complete page content, and then activate the lecture.

create_classic_lecture

Creates a Contact After calling this tool, show the user the final dashboard link: https://systeme.io/dashboard/contacts/{id}. Replace placeholders with matching tool result fields or input arguments. Do not show raw IDs, placeholders, or other internal values instead of the link.

create_contact

Creates a coupon. After calling this tool, show the user the final dashboard link: https://systeme.io/dashboard/coupons/{id}. Replace placeholders with matching tool result fields or input arguments. Do not show raw IDs, placeholders, or other internal values instead of the link.

create_coupon

Create a module inside an existing membership course for the authenticated user. Modules are appended; within one course, await each creation before creating the next module, never create them in parallel. Check each returned position against the intended order. If the target course is ambiguous, first use course search or list tools. If the module name is missing, ask the user for it.

create_course_module

Creates a digital product. Before creating, confirm the target area via source (funnel is the Funnel area, digital-store is the Creator stores area, Whitelabel is the whitelabel area), because it determines where the product is created and which fields are relevant; when the user has not specified the area, ask which one to use instead of guessing. Do not display or invent dashboard links for digital products; no public dashboard URL has been verified.

create_digital_product

Creates a funnel, optionally with its default step set for a given funnelType. Before using this tool for a user request, call describe_funnels and map the user's intent to a supported funnelType. When content is requested, use describe_page_template and resolve missing required facts before creation. When funnelType is provided, its default steps are created automatically; use create_funnel_step only for extra custom steps beyond the default set. Fill each returned step using its selected template and save_page_content_from_template; pass that templateId and the step's pageId. Creating the funnel alone does not fill its pages; an accepted content save does not confirm a finished render. Omitting funnelType creates an empty, typeless funnel with no default steps. After calling this tool, show the user the final dashboard link: https://systeme.io/dashboard/funnels/{id}. Replace placeholders with matching tool result fields or input arguments. Do not show raw IDs, placeholders, or other internal values instead of the link.

create_funnel

Creates one funnel step inside an existing funnel. Use describe_funnels first to choose the correct order and type. When content is requested, read its template and resolve missing required facts before creation. Steps are appended; within one funnel, await each creation before creating the next step, never create them in parallel. Check each returned position against the intended order. Fill the page using its selected template and save_page_content_from_template; pass that templateId, all placeholders and the step's pageId. Creating the step alone leaves its page empty; an accepted content save does not confirm a finished render.

create_funnel_step

Create a regular newsletter draft. After it is created, reply with a short success summary and point the user to the newsletter dashboard link as the next action. Do not print, paste, or restate the newsletter body or its HTML. After calling this tool, show the user the final dashboard link: https://systeme.io/dashboard/newsletters/{id}/edit. Replace placeholders with matching tool result fields or input arguments. Do not show raw IDs, placeholders, or other internal values instead of the link.

create_newsletter

Creates an offer. Use product and coupon IDs returned by their corresponding tools. Do not display or invent a dashboard link for offers; no public dashboard URL has been verified.

create_offer

Creates a physical product. Do not display or invent dashboard links for physical products; no public dashboard URL has been verified.

create_physical_product

Creates a price plan. Do not display or invent dashboard links for price plans; there is no public dashboard URL for price plans.

create_price_plan

Creates a Tag After calling this tool, show the user the final dashboard link: https://systeme.io/dashboard/tags. Replace placeholders with matching tool result fields or input arguments. Do not show raw IDs, placeholders, or other internal values instead of the link.

create_tag

Deactivate an existing course so it is not available to students. This action fails if the course is already inactive.

deactivate_course

Deactivate an existing course lecture so it is not available to students. This action fails if the lecture is already inactive.

deactivate_lecture

Deletes an automation rule. The rule stops firing and disappears from get and list results.

delete_automation_rule

Permanently deletes a booking calendar event so it no longer appears in event results or accepts new bookings. Ask the user to confirm the exact event before calling this tool.

delete_calendar_event

Delete a campaign and make its campaign steps inaccessible.

delete_campaign

Permanently delete a campaign step from an existing campaign. Call this tool only after the user explicitly asks to delete the exact step. Never use it to test activation settings, to recover from a validation error, or to replace a step: use `update_campaign_step` for changes to an existing step.

delete_campaign_step

Deletes a coupon.

delete_coupon

Delete an existing course owned by the authenticated user. Use only after the correct course has been identified.

delete_course

Delete a module from a membership course owned by the authenticated user. This also deletes all lectures in the module and may clean up related automation, workflow, and orphaned digital product resources. Use only after the correct course and module have been identified.

delete_course_module

Deletes a digital product. Do not display or invent dashboard links for digital products; no public dashboard URL has been verified.

delete_digital_product

Delete an existing membership course lecture. Use only after the correct course and lecture have been identified; deletion may remove related automation and workflow data.

delete_lecture

Delete a newsletter so it no longer appears in newsletter results or can be retrieved by ID.

delete_newsletter

Deletes a physical product. Do not display or invent dashboard links for physical products; no public dashboard URL has been verified.

delete_physical_product

Deletes a price plan. Do not display or invent dashboard links for price plans; there is no public dashboard URL for price plans.

delete_price_plan

Call once at the start of a session before creating or changing a course, then use the returned guide for the rest of that session. Returns guidance for Course, Module, and Lecture tools, including their hierarchy, operation order, required identifiers, course types, and supported constraints.

describe_courses

DEPRECATED compatibility tool. Do not use this tool for new work. To create or recreate funnel page content, use describe_page_template followed by save_page_content_from_template.

describe_funnel_page_schema

Read this before creating a funnel. Returns supported funnel shapes, step types, offer setup, and the template-based content workflow. For each page, use describe_page_template followed by save_page_content_from_template; creating the funnel or its steps alone does not fill the pages.

describe_funnels

Returns the shared MCP server instructions that define common follow-up question and answer style rules. Always call this tool before using other MCP tools.

describe_mcp_instructions

Return TipTap HTML rules for classic bodyHtml and HTML within visual bodyJson blocks. Call before generating or changing email HTML; for visual body structure also call describe_mailing_json_schema.

describe_mailing_html_guide

Return the visual email JSON schema. Call before generating or changing visual content; for HTML within blocks also call describe_mailing_html_guide.

describe_mailing_json_schema

Returns instructions for generating lecture page content. For a lecture, also read describe_page_schema, then submit the generated payload to save_content. Funnel creation and recreation use describe_page_template and save_page_content_from_template. For partial edits, use describe_page_edit_guide instead.

describe_page_content_guide

Returns the protocol for editing the content of an existing page in place, for any page type that supports AI editing. Read this before the first call to get_page_editable_content or update_page_content in an editing session. It covers the required call order, how to resolve ordinals like "the second section", and the rule that every added element must be styled by a follow-up update_page_content call. Use the editing flow instead of save_content whenever the page already has content that should be preserved.

describe_page_edit_guide

Returns the schema for generating lecture page content. For a lecture, also read describe_page_content_guide, then submit the generated payload to save_content. Funnel creation and recreation use describe_page_template and save_page_content_from_template. For partial edits, use describe_page_edit_guide instead.

describe_page_schema

Start here to create or recreate funnel page content. Returns one template chosen by Page Editor; use funnelStepType from the input schema and pass the returned templateId unchanged to save_page_content_from_template. Read one template at a time, including every complete placeholder entry and its light, alpha, guidance and targets metadata. Do not reduce the received catalogue to the first few entries or batch large descriptions into a truncated result. If the full response is inaccessible, report the limitation and do not save an incomplete set of values. Layout, blocks, spacing and typography are fixed. Write content for each field's purpose and the page's specific topic, not one generic value per type or a keyword-based filler. Repeat wording only where the template requires matching values. A different template title or sample topic alone is not a reason to reject it. There is no template catalogue to browse. Read the required templates and ask missing factual questions together before creating entities or replacing content. If the template is unavailable or cannot truthfully fulfil the request, explain the limitation and leave the funnel content unsaved.

describe_page_template

Get a single reusable automation email by ID, including its full body content.

get_automation_email

Get one specific-address automation email by ID, including its body content.

get_automation_email_to_specific_address

Get a lightweight paginated list of reusable automation emails. List items do not include body content; use get_automation_email for details. Use this tool to find the `id` of an existing automation email before referencing it from an automation rule `send_email` action.

get_automation_emails