Fansly Chat Message Action
Send messages to your Fansly stream chat when alerts trigger. Post to your main stream chat or additional channels with optional private messaging.
What You Need
- A Fansly account connected in TipLink (Settings → Platforms → Fansly)
- An active Fansly stream (or testing in stream chat when offline)
- Proper account permissions to send chat messages
Quick Start
- Connect Fansly account in TipLink (Settings → Platforms → Fansly)
- Create or edit an alert
- Add the Fansly Chat Message action
- Select your Fansly account
- Optionally select additional channels
- Enter your chat message
- Optionally enable private message
- Save and test
Configuration interface screenshot will be added here.
Configuration Options
Account Selection
Select Fansly Account
- Choose which Fansly account to send from
- Only shows accounts connected in Settings
- Required field
- Message sent from this account's identity
If you have multiple Fansly accounts connected, you can choose which one sends the message. Useful for bot accounts or multi-creator setups.
Channel Selection
Select Fansly Channel(s)
- Choose additional channels to send messages to
- Can select multiple channels
- Optional (sends to main stream chat if none selected)
- Only shows channels available for selected account
- Must have permissions for selected channels
Message Content
Chat Message
- The text to send to Fansly chat
- Supports dynamic placeholders
- Required field
- Fansly enforces message length limits (typically 1000 characters)
Dynamic Placeholders:
{username}- Viewer's username{amount}- Tip/sub amount{message}- Viewer's message{timestamp}- Event timestamp
Fansly chat supports basic text. Complex formatting, emojis, and links depend on Fansly's chat capabilities.
Privacy Options
Make this message private
- Checkbox to make message private
- When enabled: only you (the streamer) can see the message
- When disabled: message visible to all viewers in chat
- Default: disabled (public message)
Private messages are useful for personal reminders, testing, or tracking events without cluttering public chat.
Setup Guide
Connecting Fansly Account
-
Go to Settings
- TipLink → Settings → Platforms → Fansly
-
Add Fansly Account
- Click "Connect Fansly Account"
- Follow authentication flow
- Grant necessary permissions
- Account appears in TipLink
-
Verify Connection
- Check account shows as "Connected"
- Test sending a message manually
Basic Message Setup
-
Create Alert
- Navigate to Alerts
- Create new or edit existing
- Set trigger conditions
-
Add Fansly Chat Action
- Actions → Add Action
- Select "Send Fansly Chat Message"
-
Configure Message
- Select Fansly account
- Enter message:
Thanks {username} for the ${amount} tip! - Leave private message unchecked
-
Test
- Save alert
- Trigger while stream is live (or in test mode)
- Check Fansly chat
Multi-Channel Setup
To send to multiple channels:
-
Select Account
- Choose your Fansly account
-
Select Channels
- Click channel dropdown
- Hold Ctrl and select multiple channels
- Message sent to all selected channels
-
Configure Message
- Enter message content
- Same message to all channels
Private Message Setup
For personal tracking or reminders:
-
Configure Action
- Select account
- Enter message:
[Alert Triggered] {username} - ${amount}
-
Enable Private
- Check "Make this message private"
- Only you will see this in chat
-
Use Case
- Event logging without public spam
- Personal reminders during stream
- Testing without viewers seeing
Common Use Cases
Tip Acknowledgment
- Message:
Thanks {username} for the ${amount} tip! 💖 - Public thank you message
- Shows appreciation
Subscriber Welcome
- Message:
Welcome {username} to the fam! Thanks for subscribing! 🎉 - Celebrates new subscribers
- Engages community
Large Tip Alert
- Message:
🚨 HUGE TIP ALERT! {username} just tipped ${amount}! Thank you! 🚨 - Special call-out for large tips
- Extra attention for generosity
Follow Thanks
- Message:
Thanks for the follow, {username}! Welcome! 👋 - Acknowledges new followers
- Friendly greeting
Viewer Message Echo
- Message:
{username} says: {message} - Repeats viewer message
- Useful for text-to-speech or emphasis
Private Event Log
- Message:
[LOG] {username} - {event_type} - ${amount} - Private: enabled
- For personal tracking
- Doesn't clutter public chat
Milestone Celebration
- Message:
🎊 MILESTONE! {username} is our 100th subscriber! 🎊 - Special milestone messages
- Community celebration
Channel-Specific Messages
- Account: Main account
- Channels: VIP channel, General chat
- Message: Different for each (requires separate actions)
Troubleshooting
Messages not sending
- Verify Fansly account is connected
- Check account hasn't been disconnected
- Ensure stream is live or test mode is available
- Look at TipLink logs for error messages
Account not in dropdown
- Connect account in Settings → Platforms → Fansly
- Refresh TipLink if recently connected
- Check authentication hasn't expired
Channels not showing
- Verify account is selected first
- Check account has access to channels
- Channels may be stream-specific
- Refresh channel list if stale
Message appears truncated
- Fansly has message length limits
- Reduce message length
- Check for 1000 character limit
- Split into multiple actions if needed
Placeholders not replaced
- Check placeholder syntax:
{username}notusername - Verify placeholder is valid for trigger type
- Depends on event data available
Rate limiting errors
- Fansly may limit message frequency
- Add cooldowns to alerts
- Space out rapid triggers
- Check Fansly's rate limit policy
Private messages visible to others
- Verify "Make this message private" is checked
- May be platform limitation
- Test with another account to confirm
Permission errors
- Verify account has chat permissions
- Re-authenticate if permissions changed
- Check Fansly account status
- May need to reconnect account
Best Practices
Message Content:
- Keep messages concise (under 200 characters)
- Use emojis sparingly for readability
- Personalize with placeholders
- Test different message styles
- Consider chat speed/volume
Frequency:
- Use cooldowns to prevent spam
- Consider rate limiting for high-traffic streams
- Batch messages if many rapid events
- Balance engagement with chat clutter
Privacy:
- Use private messages for logging
- Public messages for engagement
- Don't spam private messages (still visible to you)
- Consider what viewers want to see
Multi-Channel:
- Send to relevant channels only
- Don't spam all channels with same message
- Consider channel purpose (VIP, General, etc.)
- Test channel permissions
Testing:
- Test messages before going live
- Verify placeholders work correctly
- Check message length
- Test private vs public behavior
- Confirm channel targeting
Account Management:
- Use consistent account for branding
- Consider bot account for automated messages
- Keep accounts authenticated
- Re-authenticate periodically if needed
Technical Reference
Fansly API:
- Uses Fansly's chat API
- Requires authenticated account
- Subject to Fansly rate limits
- Messages sent via HTTP requests
Message Limits:
- Typical max length: ~1000 characters
- Subject to Fansly's policies
- May vary by account type
- Enforced server-side
Rate Limits:
- Fansly enforces rate limits per account
- Exact limits not publicly documented
- Typically generous for normal use
- Exceeded limits return errors
Authentication:
- OAuth-based authentication
- Tokens stored securely
- May expire and need refresh
- Re-authentication required if expired
Channel Access:
- Channels depend on account permissions
- Stream-specific channels
- VIP/subscriber channels if applicable
- List refreshed periodically
Private Messages:
- Sent to chat but marked private
- Only visible to account owner (streamer)
- Other viewers cannot see
- Appears in your chat interface
Placeholders:
- Processed before sending
- Depends on event type
- Invalid placeholders remain as-is
- Case-sensitive
Error Handling:
- Errors logged to TipLink console
- No automatic retry
- Rate limit errors reported
- Network errors fail silently (logged)
Message Delivery:
- Asynchronous (non-blocking)
- No delivery confirmation to TipLink
- Fansly handles delivery to viewers
- Network latency: typically 100-500ms
Account Types:
- Creator accounts (your stream)
- Bot accounts (if supported)
- Multi-account support
- Each account authenticated separately
Platform Limitations:
- Message features depend on Fansly
- Private message support may vary
- Channel types platform-specific
- Subject to Fansly updates
Security:
- OAuth tokens stored securely
- No password storage
- Tokens encrypted at rest
- Re-authentication invalidates old tokens
Performance:
- Minimal overhead per message
- Multiple accounts supported simultaneously
- No local message queue
- Direct API calls to Fansly