Integration

Flodesk integration

Flodesk is email marketing software for creators and small businesses. Create, update and look up subscribers one at a time or 50 at a time, add them to or remove them from segments, unsubscribe them, start or stop a workflow (an automated email sequence) for a subscriber, create and list segments and custom fields, list workflows, and manage webhooks for subscriber events. Subscribers are personal data, and starting a workflow, adding a subscriber to a segment that triggers one, or asking for double opt-in emails the subscriber. Left out: campaigns, which the public API reference does not cover, and the OAuth flow reserved to approved partner apps. Authentication is HTTP Basic with a Flodesk API key (created on the API Key page of your Flodesk account) as user name and a blank password, entered as the Base64 of the key followed by a colon.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Flodesk.Built from the 22 Flodesk tools below, on the connection you add once.

What you can do with Flodesk

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Segment, 5 operations

  • add_subscriber_to_segmentsAdd subscriber to segmentsPOSTAdds a subscriber to one or more segments and returns the updated subscriber. A segment that triggers a workflow starts that workflow for them, which emails them.
  • create_segmentCreate segmentPOSTCreates a segment (a group of subscribers) with a name and a color, and returns it with its id.
  • get_segmentGet segmentGETReturns one segment with its name, color, type (static or dynamic), creation date and number of active subscribers.
  • list_segmentsList segmentsGETLists your segments page by page with their id, name, color, type (static or dynamic), creation date and number of active subscribers.
  • remove_subscriber_from_segmentsRemove subscriber from segmentsDELETERemoves a subscriber from one or more segments and returns the updated subscriber. Workflows they are already in keep running: use remove_subscriber_from_workflow to stop those emails.

Subscriber, 5 operations

  • add_subscriber_to_workflowAdd subscriber to workflowPOSTStarts a workflow (an automated email sequence) for a subscriber, who then receives its emails. Repeat entry needs the workflow's Allow repeat subscribers setting and a finished previous run; no abandoned cart workflows.
  • create_or_update_subscriberCreate or update subscriberPOSTCreates a subscriber, or updates the one with that email or id: names, custom fields, segments, opt-in details. A segment that triggers a workflow starts it, and double_optin on a new subscriber sends a confirmation email. Personal data.
  • get_subscriberGet subscriberGETReturns one subscriber, looked up by id or email: status, names, source, segments, custom fields, opt-in IP and time. Personal data.
  • list_subscribersList subscribersGETLists subscribers page by page, optionally only one status or one segment: email, names, status, source, segments, custom fields, opt-in IP and time. Personal data.
  • remove_subscriber_from_workflowRemove subscriber from workflowDELETERemoves a subscriber from a workflow (an automated email sequence).

Webhook, 5 operations

  • create_webhookCreate webhookPOSTCreates a webhook: Flodesk will POST the chosen subscriber events (subscriber.created, subscriber.added_to_segment, subscriber.unsubscribed) to post_url.
  • delete_webhookDelete webhookDELETEDeletes a webhook, so its events stop being sent.
  • get_webhookGet webhookGETReturns one webhook with its enabled events and creation date (the destination URL is not returned).
  • list_webhooksList webhooksGETLists your webhooks page by page with their id, enabled events and creation date (the destination URL is not returned).
  • update_webhookUpdate webhookPUTUpdates a webhook's name, destination URL or enabled events.

Custom field, 2 operations

  • create_custom_fieldCreate custom fieldPOSTCreates a subscriber custom field from a display label and returns its key, the name to use in a subscriber's custom_fields.
  • list_custom_fieldsList custom fieldsGETLists your subscriber custom fields page by page, each with its key (the name used in a subscriber's custom_fields) and its display label.

All, 1 operation

  • list_all_custom_fieldsList all custom fieldsGETLists every subscriber custom field in one answer, each with its key (the name used in a subscriber's custom_fields) and its display label.

Batch, 1 operation

  • batch_create_or_update_subscribersBatch create or update subscribersPOSTCreates or updates up to 50 subscribers in one call; returns the successes and, per failed item, its index, code and message. Segments that trigger a workflow start it; double_optin emails new ones. 20 calls per minute. Personal data.

Color, 1 operation

  • list_segment_colorsList segment colorsGETLists the hex colors a segment may use, the values create_segment accepts as color.

Unsubscribe, 1 operation

  • unsubscribe_subscriberUnsubscribe subscriberPOSTUnsubscribes a subscriber from all lists, so they stop receiving marketing emails, and returns the updated subscriber.

Workflow, 1 operation

  • list_workflowsList workflowsGETLists your workflows (automated email sequences) with their id and name, optionally only some statuses.

Use Flodesk from Claude Code, Cursor or Codex

Connect Flodesk in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Flodesk operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Flodesk

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Flodesk once

    Add your Flodesk connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Flodesk integration FAQ

What can you do with the Flodesk integration?

LiveContext exposes 22 operations on Flodesk, covering segment, subscriber, webhook and custom field.

Popular integrations

Browse the whole catalog