Marketing Automation
Flodesk
Connect Flodesk once and hand every teammate a governed MCP endpoint with 18 tools ready to call from Claude, ChatGPT, Cursor, or any MCP client, inside the same permissions they already have, with every call checked and logged.
Automations & dashboards
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards ship on the Black plan.
Automations
Put Flodesk work on a schedule.
A trigger starts a sequence of steps: call a Flodesk tool, transform the result, branch, wait, and ask a person when it matters.
Flodesk digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch webhooks
Flodesk
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Flodesk
Queued
Collections and dashboards
Report on Flodesk without asking.
Collections hold your own data, written by an automation and read by a dashboard that refreshes on a schedule.
Flodesk health
Refreshed 4 minutes ago · every 15 minutes · from the webhooks collection
Webhooks
1,284 ↓ 12%
Subscribers
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Webhooks created
Last 14 days
By workspace
Share of activity
Engineering 34%
Product 27%
Support 21%
Sales 18%
AI tools
Flodesk tools for your AI agents
18 tools are ready to call through Elaichi's MCP endpoint the moment you connect Flodesk, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
list_all_flodesk_segments
List all segments in Flodesk. Returns id, name, total_active_subscribers, created_at, and color for each segment.
get_single_flodesk_segment_by_id
Get details of a specific segment in Flodesk using id. Returns id, name, total_active_subscribers, created_at, and color fields in the response.
create_a_flodesk_segment
Create a segment in Flodesk. Requires name and color. Returns id, name, total_active_subscribers, created_at, and color in the response.
list_all_flodesk_subscribers
List all subscribers in Flodesk. Returns each subscriber's id, status, email, first_name, last_name, segments, custom_fields, optin_ip, optin_timestamp, and created_at.
get_single_flodesk_subscriber_by_id
Get a specific subscriber in Flodesk using id_or_email. Returns id, status, email, source, name fields, segments, custom_fields, optin_ip, optin_timestamp, and created_at.
create_a_flodesk_subscriber
Create or update a subscriber in Flodesk using email or id. Returns subscriber details including id, status, email, source, first_name, last_name, segments, custom_fields, optin_ip, optin_timestamp, and created_at.
delete_a_flodesk_subscriber_by_id
Remove a subscriber from segments in Flodesk. Requires id_or_email and segment_ids. Returns subscriber details including id, status, email, segments, and custom_fields.
list_all_flodesk_segment_colors
List all available segment colors in Flodesk. Returns an array of color strings representing the available segment color options.
list_all_flodesk_workflows
List workflows in Flodesk. Returns an array of workflows with fields id and name for each workflow.
create_a_flodesk_workflow
Add a subscriber to a workflow in Flodesk. Requires id for the workflow and either subscriber id or email. Subscribers must not be active or in abandoned cart workflows. Returns subscriber details and workflow status.
delete_a_flodesk_workflow_by_id
Remove a subscriber from a specific workflow in Flodesk. Requires workflow_id and id. Returns 204 on success or 404 if not found.
list_all_flodesk_custom_fields
List all custom fields in Flodesk. Returns key and label for each field.
create_a_flodesk_custom_field
Create a custom field in Flodesk using the required parameter label. Returns details of the created custom field, including its id, label, and metadata.
list_all_flodesk_webhooks
List all webhooks in Flodesk. Returns webhook details including id, event type, target URL, and creation timestamp.
get_single_flodesk_webhook_by_id
Get details of a specific webhook in Flodesk using id. Returns webhook configuration fields including the event type, target URL, and status.
create_a_flodesk_webhook
Create a webhook in Flodesk. Requires name, post_url, and events. Returns id, post_url, events, and created_at fields in the response.
update_a_flodesk_webhook_by_id
Update a webhook in Flodesk using id. Returns id, post_url, events, and created_at fields describing the updated webhook configuration.
delete_a_flodesk_webhook_by_id
Delete a webhook in Flodesk using id. Returns 204 on successful deletion or 404 if the specified webhook is not found.
No tools match your search.
How it works
From Flodesk account to governed MCP endpoint
Connect
Link a Flodesk account through Elaichi's hosted connect flow. Credentials are vaulted, so nobody, including the AI, ever sees them.
Compose
The connection becomes a toolbox instantly. Curate which Flodesk tools are exposed, rename them, or freeze arguments.
Authorize
Point Claude, ChatGPT, Cursor, or any MCP client at the one Elaichi endpoint and sign in with OAuth, governed by roles, restrictions, and audit logs.
Put your agents to work in the tools you already use
Start a 14-day Gold trial. Connect a product, curate a toolbox, and paste a governed MCP endpoint into Claude, ChatGPT, or Cursor in minutes.