Welcome messages, drip sequences, saved quick replies, and AI-drafted responses are all endpoints. Automate the repetitive chat work and keep chatters focused on closing.
# set a welcome drip for new subscribers curl https://api.fanduit.co/v1/accounts/$id/auto-messages \ -H "Authorization: Bearer sk_live_…" \ -d '{ "trigger": "new_sub", "text": "Hey 👋 welcome!" }' → 201 Created ● active
Repetitive messaging handled by the API.
Fire automated messages on triggers like a new subscription or a set delay.
Store canned quick replies your chatters can reuse across conversations.
Have FansBot read a chat and draft an on-brand reply for a human to send.
Pair automation with human-paced mass campaigns to a segment.
Retry safely with an idempotency key so a fan never gets a double message.
Trigger automations from webhooks in Zapier, Make, or n8n.
Trigger, message, measure.
Choose an event like a new sub or a delay after subscribing.
Compose the auto-message or pick a saved reply.
Fanduit sends on the trigger, metered and idempotent.
Less busywork, more closing.
Greet every new fan the moment they subscribe.
Send timed follow-ups to warm fans toward a purchase.
Give chatters AI-drafted replies to move faster without losing voice.
Keep messaging on-brand across a whole roster with shared saved replies.
Run a whole roster from one API — connect every creator you operate and automate messaging, growth, and reporting at scale.
Neutral infrastructure on accounts you own, with encrypted credentials, per-account proxies, and no screen sharing.
Clean REST + MCP, signed webhooks, idempotency, and transparent credit metering. Build tools that don\'t break by morning.
Sends run through the same paced, signed, proxied path as manual messages, and idempotency prevents double-sends.
FansBot can draft replies from the chat context for a human to review and send. Version one keeps a human in the loop.
New subscription, delays, and events you wire through webhooks into your own logic.
Set a welcome flow in one call.