Platform Overview
Chirpify transforms TradingView alerts into intelligent, filtered notifications that help you make better trading decisions. Perfect for traders using private indicators who want to reduce noise and improve signal quality without modifying code.
Key Concepts
๐จ Alert Groups
Collections of related alerts with shared filtering logic. Think of them as smart folders that process incoming signals based on your rules.
๐ Webhooks
The bridge between TradingView and Chirpify. Your alerts are sent to unique webhook URLs where they're processed and filtered.
๐ข Chirps
Filtered alert notifications delivered to your preferred channels (Telegram, email, webhooks, or trading platforms).
โก Channels
Delivery destinations for your chirps - configure Telegram bots, email addresses, webhooks, or crypto exchange connections.
๐ก Why Chirpify?
Many traders use premium TradingView indicators they can't modify. Chirpify lets you add sophisticated filtering on top of any indicator without touching the source code - perfect for reducing false signals and combining multiple indicators intelligently.
Account Setup
Get started with Chirpify in just a few minutes.
Creating Your Account
- Visit app.chirpify.dev/signup
- Enter your email address and create a secure password
- Verify your email address by clicking the link sent to your inbox
- Complete the onboarding flow to set up your first alert group
Plan Selection
Choose the plan that fits your trading needs:
Alert Builder ($15/month)
- 5 alert groups
- 10 chirps per day
- Telegram integration
- Basic analytics
Signal Amplifier ($25/month)
- 10 alert groups
- 30 chirps per day
- All integrations
- Advanced analytics
Chirpify Elite ($49/month)
- Unlimited alert groups
- Unlimited chirps
- Crypto exchange trading
- Priority support
Authentication
Chirpify uses secure authentication to protect your trading data and configurations.
Sign-In Methods
- Email/Password: Traditional authentication with your email and password
- Google OAuth: Sign in with your Google account for faster access
Security Features
- All data encrypted in transit and at rest
- Session timeouts for inactive accounts
- Secure API key management for exchange connections
- No storage of withdrawal permissions
โ ๏ธ Security Best Practices
- Use a strong, unique password for your Chirpify account
- Never share your webhook URLs publicly
- Regularly review connected exchange permissions
- Enable two-factor authentication on your exchange accounts
Telegram Bot Setup
Connect Chirpify to Telegram to receive filtered alerts directly in your chat.
Step-by-Step Setup
-
Start a chat with BotFather
Open Telegram and search for
@BotFather
or click here -
Create your bot
Send
/newbot
to BotFather and follow the prompts:/newbot Choose a name for your bot: My Trading Alerts Choose a username for your bot: mytradingalerts_bot
-
Get your bot token
BotFather will provide a token like
123456789:ABCdefGHIjklMNOpqrsTUVwxyz
Important: Keep this token secure! Anyone with this token can control your bot.
-
Configure in Chirpify
In your Chirpify dashboard:
- Go to Channels โ Add Channel โ Telegram
- Paste your bot token
- Click "Test Connection" to verify
Telegram Bot Configuration
Finding Your Chat ID
To send messages to a specific chat, you need the Chat ID:
For Private Messages
- Start a chat with your bot by searching for its username
- Send any message to the bot (like
/start
) - In Chirpify, click "Get Chat ID" - it will show your personal chat ID
For Groups/Channels
- Add your bot to the group/channel as an administrator
- Send a message mentioning the bot (e.g.,
@yourbotname hello
) - In Chirpify, click "Get Chat ID" to see available group IDs
Chat ID Examples
- Private chat:
123456789
- Group chat:
-987654321
- Channel:
-1001234567890
Telegram Channels & Groups
Setting Up Channels
Telegram channels are perfect for broadcasting alerts to multiple subscribers:
- Create a new channel in Telegram
- Add your bot as an administrator with "Post Messages" permission
- Configure the channel ID in Chirpify
Group Configuration
Groups allow interactive alerts and discussions:
- Create or join a Telegram group
- Add your bot with appropriate permissions
- Configure group privacy settings as needed
Message Formatting
Customize how your alerts appear in Telegram:
๐จ ALERT TRIGGERED ๐จ Symbol: {{symbol}} Price: ${{price}} Signal: {{action}} Time: {{timestamp}}
Testing Telegram Delivery
Send Test Message
Verify your Telegram configuration by sending a test message:
- Go to Channels in your Chirpify dashboard
- Find your Telegram channel configuration
- Click "Send Test Message"
- Check your Telegram chat for the test message
Common Issues
Bot not responding
- Verify the bot token is correct
- Check that the bot is not blocked
- Ensure the bot has permission to send messages
Messages not appearing in group
- Confirm the bot is added as an administrator
- Check the chat ID is correct (negative for groups)
- Verify group privacy settings allow bots
General Exchange Setup
Connect Chirpify to crypto exchanges for automated trading based on your filtered alerts.
Security Best Practices
๐ API Key Security
- Never enable withdrawal permissions - Chirpify only needs trading permissions
- Use IP whitelisting when available
- Create dedicated API keys for Chirpify (don't reuse existing keys)
- Regularly rotate API keys and secrets
- Monitor your exchange account for unusual activity
Required Permissions
For each exchange, ensure your API key has these permissions:
- โ Read account information (balances, positions)
- โ Create orders (market and limit orders)
- โ Cancel orders (modify existing orders)
- โ Withdraw funds (never enable this)
Testnet vs Mainnet
Start with testnet environments to verify your setup before live trading:
Environment | Purpose | Funds | Risk |
---|---|---|---|
Testnet | Testing and development | Fake/demo funds | Zero risk |
Mainnet | Live trading | Real funds | Real money at risk |
Bybit Integration
Creating API Keys
- Log into your Bybit account
- Go to API Management โ Create New Key
- Select permissions:
- โ Account Info
- โ Order
- โ Position
- โ Withdraw (never enable)
- Add IP restrictions for security (optional but recommended)
- Save your API Key and Secret securely
Configuration in Chirpify
- Go to Channels โ Add Channel โ Bybit
- Enter your API Key and Secret
- Select environment (Testnet for testing, Mainnet for live trading)
- Configure default order settings:
- Order type (Market/Limit)
- Position sizing method
- Default quantity or percentage
- Click "Test Connection" to verify
Order Configuration
Binance Integration
API Key Setup
- Access Binance API Management in your account settings
- Create a new API key with a descriptive name (e.g., "Chirpify Trading")
- Configure permissions:
- โ Enable Spot & Margin Trading
- โ Enable Futures Trading (if needed)
- โ Enable Withdrawals (never enable)
- Set up IP access restriction for enhanced security
- Note down your API Key and Secret Key
Binance-Specific Features
- Spot Trading: Trade spot markets with immediate settlement
- Futures Trading: Access to Binance Futures markets
- Advanced Order Types: Support for OCO and other advanced orders
- Sub-account Support: Trade with sub-account API keys
๐ก Binance Tips
- Use Binance Testnet for initial testing
- Consider using sub-accounts for organization
- Monitor your daily trading limits
- Enable IP whitelisting for maximum security
KuCoin Integration
Three-Part Authentication
KuCoin uses a three-part authentication system:
- API Key: Your public identifier
- Secret Key: Used for request signing
- Passphrase: Additional security layer you create
Setup Process
- Go to KuCoin API Management
- Create a new API with these settings:
- API Name: "Chirpify Trading Bot"
- Passphrase: Create a strong passphrase (save this!)
- Permissions: Trade only (no withdrawal)
- Configure IP whitelist (recommended)
- Save all three values: API Key, Secret Key, and Passphrase
Configuration in Chirpify
API Key: 5c2db93503aa674c74ed2e3a Secret: f03a5284-5c39-4aaa-9b20-dea1014b86c6 Passphrase: YourSecurePassphrase123
โ ๏ธ KuCoin Security Notes
- The passphrase is not recoverable - save it securely
- API keys expire after 6 months of inactivity
- Always test with small amounts first
Hyperliquid Integration
Wallet-Based Authentication
Hyperliquid uses wallet-based authentication instead of traditional API keys:
-
Create a Trading Wallet
Set up a dedicated wallet for Chirpify trading:
- Create a new wallet or use an existing one
- Fund it with appropriate amounts for trading
- Note the wallet address (starts with 0x...)
-
Export Private Key
โ ๏ธ Critical Security Warning: Private keys provide full access to your wallet. Only use dedicated trading wallets with limited funds.
- Export the private key from your wallet
- Keep this extremely secure
- Never share or expose this key
-
Configure in Chirpify
- Go to Channels โ Add Channel โ Hyperliquid
- Enter your wallet's private key
- Select network (Testnet/Mainnet)
- Test the connection
Hyperliquid Features
- Perpetual Futures: Trade perpetual contracts with high leverage
- Low Fees: Competitive trading fees
- Fast Execution: High-performance trading engine
- Advanced Orders: Support for sophisticated order types
๐ก Hyperliquid Best Practices
- Use a dedicated wallet with limited funds
- Start with testnet to verify integration
- Monitor gas costs for transactions
- Keep private keys encrypted and secure
Testing & Verification
Connection Testing
Always verify your exchange connections before live trading:
- Test API Connection: Click "Test Connection" in channel settings
- Verify Account Access: Check that balances load correctly
- Small Test Order: Place a minimal test order
- Monitor Execution: Confirm orders execute as expected
Portfolio Tracking
Monitor your connected exchange accounts:
- View real-time balances across all connected exchanges
- Track open positions and orders
- Monitor P&L and trading performance
- Review order history and execution logs
Order Verification
Pre-Live Checklist
- โ API keys have correct permissions
- โ Withdrawal permissions are disabled
- โ Test orders execute successfully
- โ Position sizing calculations are correct
- โ Risk management rules are in place
- โ Alert groups are properly configured
Creating Alert Groups
Alert groups are the core of Chirpify's filtering system. They define how incoming alerts are processed and when chirps are sent.
Basic Alert Group Setup
-
Create a New Group
Go to Alert Groups โ Create New Group
-
Choose Group Type
- Simple Filter: Basic alert filtering with conditions
- Logic Group: Complex AND/OR/NOT logic combinations
- Sequence Group: Alerts that must occur in specific order
-
Configure Basic Settings
- Group name and description
- Target symbols/tickers
- Delivery channels
- Active time windows
Alert Group Components
๐ฅ Triggers
Define what incoming alerts activate this group (symbol, message content, source indicator)
๐ Filters
Conditions that must be met for alerts to pass through (price ranges, time windows, rate limits)
๐ค Actions
What happens when filters pass (send to Telegram, execute trade, trigger webhook)
โฐ Timing
When the group is active (trading hours, specific days, silence periods)
Boolean Logic (AND/OR/NOT)
Create sophisticated filtering rules using boolean logic to combine multiple conditions.
Logic Operators
AND Logic
ALL conditions must be true
RSI > 70 AND Volume > Average AND Price > $50
Only triggers when RSI is overbought, volume is high, AND price exceeds $50
OR Logic
ANY condition can be true
MACD_Bullish OR MA_Cross_Up OR Breakout_Pattern
Triggers when any of the three indicators signals bullish
NOT Logic
Condition must NOT be true
Strong_Buy AND NOT Market_Close_Soon
Only triggers buy signals when market isn't closing soon
Complex Logic Examples
// Conservative entry strategy (Momentum_Buy AND Volume_Spike) AND (NOT Overbought_RSI) AND (Market_Hours OR Crypto_24h) // Confirmation from multiple indicators (Indicator_A_Buy OR Indicator_B_Buy) AND (Volume > 1.5x_Average) AND (NOT Recent_Alert_15min)
Building Logic Rules
- Start with simple conditions
- Use parentheses to group related conditions
- Test with historical data when possible
- Add time-based conditions to prevent spam
- Include risk management filters
Nesting & Hierarchy
Create hierarchical alert structures where groups can depend on other groups.
Parent-Child Relationships
๐ฏ Master Trading Strategy
๐ Bullish Signals
- MA crossover alerts
- RSI oversold recovery
- Breakout patterns
๐ Bearish Signals
- Resistance rejections
- RSI overbought
- Breakdown patterns
โ ๏ธ Risk Management
- Stop loss triggers
- Position size limits
- Market condition filters
Dependency Rules
- Require Parent: Child only triggers if parent has triggered recently
- Block on Parent: Child won't trigger if parent has triggered
- Inherit Settings: Child uses parent's timing and rate limit settings
- Override Settings: Child has its own independent settings
Use Cases for Nesting
Strategy Confirmation
Require signals from multiple timeframes or indicators before acting
Risk Layering
Apply different risk rules based on market conditions or volatility
Portfolio Management
Organize alerts by asset class, sector, or trading strategy
Value Conditions & Thresholds
Set specific conditions based on price, volume, and indicator values to fine-tune your filtering.
Price Conditions
Absolute Price Filters
Price > $100
- Only high-value stocksPrice < $50 AND Price > $10
- Mid-cap rangePrice_Change > 5%
- Significant moves only
Relative Price Filters
Price > EMA_20
- Above moving averagePrice_vs_VWAP > 2%
- Above volume weighted averageDistance_from_High < 5%
- Near recent highs
Volume Conditions
// Volume-based filters Volume > Average_Volume * 2.0 // High volume spike Volume_Ratio > 1.5 // Above normal volume Dollar_Volume > $1M // Minimum liquidity Unusual_Volume_Spike = true // Detected volume anomaly
Technical Indicator Conditions
RSI Conditions
RSI > 70
- Overbought territoryRSI < 30
- Oversold territoryRSI_Divergence = true
- Bullish/bearish divergence
MACD Conditions
MACD > Signal_Line
- Bullish crossoverMACD_Histogram > 0
- Increasing momentumMACD_Slope > 0.1
- Strong momentum change
Time-Based Conditions
- Market Hours: Only during regular trading hours
- Day of Week: Exclude weekends or specific days
- Time Windows: Active only during specified hours
- Session Filters: Pre-market, regular hours, after-hours
Sequence-Based Alerts
Create alerts that trigger only when events occur in a specific order within defined time windows.
Sequence Concepts
Setup Phase
Initial condition met (e.g., breakout above resistance)
Confirmation Phase
Follow-up condition within time window (e.g., volume increase)
Trigger Phase
Final condition triggers the alert (e.g., momentum confirmation)
Sequence Examples
Breakout Confirmation Sequence
- Step 1: Price breaks above resistance level
- Step 2: Volume increases 2x within 15 minutes
- Step 3: Price stays above breakout level for 30 minutes
- Result: Send confirmed breakout alert
Reversal Pattern Sequence
- Step 1: RSI oversold (< 30)
- Step 2: Bullish divergence detected within 4 hours
- Step 3: Price closes above key moving average
- Result: Potential reversal confirmed
Sequence Configuration
Time Windows
- Step Timeout: Maximum time between sequence steps
- Total Timeout: Maximum time for entire sequence
- Reset Conditions: When to restart the sequence
Failure Handling
- Timeout Action: What happens when sequence times out
- Reset Triggers: Conditions that invalidate the sequence
- Partial Alerts: Notify on incomplete sequences
Rate Limiting & Delivery Modes
Control the frequency and timing of your alerts to prevent notification fatigue and improve signal quality.
Rate Limiting Options
๐ Time-Based Limits
- Maximum alerts per hour/day
- Minimum time between alerts
- Cooldown periods after triggers
๐ Count-Based Limits
- Max alerts per symbol
- Max alerts per trading session
- Rolling window limits
๐ฏ Adaptive Limits
- Reduce rate during low volatility
- Increase rate during high activity
- Smart spam detection
Delivery Modes
๐จ Immediate Mode
Send alerts as soon as conditions are met
- Best for: High-frequency trading, breaking news
- Risk: Can create notification overload
๐ฆ Batch Mode
Collect and send alerts in groups
- Best for: Market summaries, multiple symbols
- Options: Every 15min, hourly, daily
๐ฏ Smart Mode
AI-powered delivery timing optimization
- Learns your response patterns
- Avoids sending during inactive periods
- Prioritizes high-confidence signals
Silence Periods
Define when alerts should NOT be sent:
- Trading Hours: Only during market open
- Personal Schedule: Respect your sleep/work schedule
- Market Conditions: Pause during high volatility or low liquidity
- Temporary Disable: Vacation mode or maintenance windows
Rate Limiting Configuration Example
Alert Group: "High-Conviction Trades" โโโ Rate Limits: โ โโโ Max 5 alerts per hour โ โโโ Min 30 minutes between same-symbol alerts โ โโโ Max 20 alerts per trading day โโโ Delivery Mode: Smart (immediate for score > 8.0) โโโ Silence Periods: โ โโโ Weekends (unless crypto) โ โโโ 11 PM - 6 AM (local time) โ โโโ Major market holidays โโโ Escalation: Email backup if Telegram fails
Setting Up TradingView Alerts
Connect your TradingView indicators to Chirpify using webhooks - works with any indicator, private or public.
TradingView Alert Creation
-
Open Your Chart
Navigate to the chart with your indicator and desired symbol
-
Create Alert
Click the alert icon in the top toolbar or press Alt+A
-
Configure Alert Condition
- Select your indicator from the dropdown
- Choose the specific condition (crossing, above/below value, etc.)
- Set any required threshold values
-
Set Alert Actions
- Enable "Webhook URL" option
- Paste your Chirpify webhook URL
- Configure the message format (see payload section)
Getting Your Webhook URL
- Go to your Chirpify Alert Groups
- Select or create an alert group
- Copy the webhook URL from the group settings
- Each alert group has a unique webhook URL
Example Webhook URL
https://webhooks.chirpify.dev/alerts/abc123def456 โ ๏ธ Keep this URL private - anyone with it can send alerts to your group
Alert Frequency Settings
- Once Per Bar Close: Alert triggers only at candle close
- Once Per Bar: First trigger per candle, then waits for next bar
- All: Triggers every time condition is met (can cause spam)
๐ก Best Practices
- Use "Once Per Bar Close" for most reliable signals
- Test your alerts with paper trading first
- Include symbol and timeframe in alert messages
- Use descriptive names for different alert types
Webhook Configuration
Configure your TradingView webhook settings to send properly formatted alerts to Chirpify.
Webhook URL Setup
In TradingView Alert Settings:
- Check "Send webhook" option
- Paste your Chirpify webhook URL
- Ensure the URL is exactly as provided (no extra characters)
Message Configuration
The message you configure in TradingView becomes the payload sent to Chirpify. Use these variables:
Available TradingView Variables
Variable | Description | Example |
---|---|---|
{{ticker}} |
Symbol name | AAPL, BTCUSDT |
{{close}} |
Current close price | 150.25 |
{{volume}} |
Current volume | 1234567 |
{{time}} |
Alert timestamp | 2025-01-15T10:30:00Z |
{{interval}} |
Chart timeframe | 5m, 1h, 1D |
Security Considerations
๐ Webhook Security
- Never share webhook URLs publicly
- Regenerate URLs if compromised
- Use unique URLs for different strategies
- Monitor for unexpected alert volume
Webhook Limits
TradingView Limitations
- Payload Size: Maximum 1KB per webhook
- No Authentication: TradingView doesn't support auth headers
- Rate Limits: Varies by TradingView plan
- Timeout: 10-second timeout for webhook delivery
Payload Format & Requirements
Structure your TradingView alert messages for optimal processing by Chirpify.
Recommended JSON Format
{ "symbol": "{{ticker}}", "action": "BUY", "price": {{close}}, "volume": {{volume}}, "timestamp": "{{time}}", "timeframe": "{{interval}}", "strategy": "My Momentum Strategy", "confidence": 8.5, "stop_loss": 145.50, "take_profit": 155.75 }
Simple Text Format
For basic setups, you can use simple text messages:
SIGNAL: BUY {{ticker}} at {{close}} | Volume: {{volume}} | Time: {{time}}
Advanced Payload Examples
Scalping Strategy
{ "signal_type": "SCALP", "symbol": "{{ticker}}", "entry_price": {{close}}, "direction": "LONG", "risk_reward": 1.5, "timeframe": "{{interval}}", "volume_spike": true, "rsi": 65.2 }
Swing Trading Strategy
{ "strategy": "SWING_MOMENTUM", "ticker": "{{ticker}}", "signal": "ENTRY", "price": {{close}}, "target_1": 155.00, "target_2": 160.00, "stop_loss": 145.00, "position_size": "2%", "market_cap": "LARGE" }
Required Fields
For optimal processing, include these minimum fields:
- Symbol: Asset identifier (ticker, pair)
- Action/Signal: What action to take (BUY, SELL, HOLD)
- Price: Current or trigger price
- Timestamp: When the signal occurred
Field Validation
Data Type Requirements
- Numbers: Price, volume, indicators should be numeric
- Strings: Symbol, action, strategy names
- Timestamps: ISO format preferred (YYYY-MM-DDTHH:mm:ssZ)
- Booleans: true/false for binary conditions
Testing Webhook Delivery
Verify your TradingView webhook integration is working correctly before relying on it for live trading.
Testing Process
-
Create Test Alert
Set up a simple alert that triggers frequently for testing:
- Use a short timeframe (1 or 5 minutes)
- Choose a simple condition (price crosses moving average)
- Set to trigger "All" instead of "Once Per Bar"
-
Monitor Delivery
Check multiple places for successful delivery:
- Chirpify Alert Activity logs
- Your configured delivery channels (Telegram, email)
- Browser developer tools for webhook calls
-
Verify Payload
Ensure the data arrives as expected:
- All variables are properly substituted
- JSON format is valid (if using JSON)
- Required fields are present
Testing Tools
๐ Chirpify Activity Monitor
View real-time alert processing in your dashboard
- See incoming webhook requests
- Monitor filter processing
- Track delivery success/failures
๐ Browser Developer Tools
Monitor network requests from TradingView
- Open DevTools (F12) in TradingView
- Go to Network tab
- Filter for your webhook URL
- Check response codes and timing
Common Test Scenarios
๐ Basic Connectivity
- Simple price alert with basic message
- Verify webhook receives the alert
- Check delivery to one channel
๐ Complex Payload
- Multi-field JSON message
- Multiple TradingView variables
- Verify all fields parse correctly
โก High Frequency
- Rapid-fire alerts (every bar)
- Test rate limiting behavior
- Verify no alerts are dropped
TradingView Troubleshooting
Resolve common issues with TradingView webhook integration.
Common Issues & Solutions
โ Webhooks Not Firing
Symptoms:
- Alert shows as created but no webhook received
- No activity in Chirpify logs
Solutions:
- โ Verify webhook URL is exactly correct
- โ Check "Send webhook" is enabled in alert
- โ Confirm your TradingView plan supports webhooks
- โ Test with a simple alert first
๐ Variables Not Substituted
Symptoms:
- Receiving literal "{{ticker}}" instead of symbol
- Message shows variable names not values
Solutions:
- โ
Use double curly braces:
{{ticker}}
- โ Check variable spelling exactly
- โ Ensure variables are supported for your alert type
- โ Test with basic variables first (ticker, close)
โฑ๏ธ Delayed or Missing Alerts
Symptoms:
- Alerts arrive minutes late
- Some alerts never arrive
- Inconsistent delivery timing
Solutions:
- โ Check TradingView server status
- โ Verify alert frequency settings
- โ Monitor for rate limiting
- โ Consider using "Once Per Bar Close"
๐ฑ Invalid JSON Format
Symptoms:
- "JSON parse error" in Chirpify logs
- Alerts received but not processed
Solutions:
- โ Validate JSON syntax with online validator
- โ Use proper quotes around string values
- โ Escape special characters in strings
- โ Test with simple text format first
Debugging Steps
-
Check TradingView Alert Status
Verify the alert is active and configured correctly
-
Monitor Network Traffic
Use browser dev tools to see if webhook requests are being sent
-
Review Chirpify Logs
Check the Activity section for incoming webhook requests
-
Test with Minimal Configuration
Start with the simplest possible alert and gradually add complexity
-
Contact Support
If issues persist, contact support with specific error messages and examples
Webhook Testing URLs
Use these tools to test webhook delivery independently:
- webhook.site: Temporary URLs for testing webhook delivery
- httpbin.org: Simple HTTP request inspector
- ngrok: Tunnel to local development server
Analytics & Monitoring
Track the performance and effectiveness of your alert filtering with comprehensive analytics.
Dashboard Overview
๐ Alert Volume
- Incoming alerts per hour/day
- Filtered vs. delivered ratios
- Peak activity periods
๐ฏ Filter Effectiveness
- False positive reduction rate
- Signal quality improvements
- Most/least effective filters
โก Performance Metrics
- Processing latency
- Delivery success rates
- System uptime statistics
๐ฐ Trading Results
- Automated trade success rates
- P&L tracking by strategy
- Risk-adjusted returns
Alert Group Analytics
Detailed performance metrics for each alert group:
- Trigger Frequency: How often each group activates
- Filter Performance: Which conditions are most effective
- Delivery Success: Channel reliability and timing
- User Engagement: How often you act on different alert types
Custom Reports
๐ Performance Report
Weekly/monthly summaries of alert effectiveness and trading outcomes
๐ Filter Optimization
Recommendations for improving your alert group configurations
๐จ Alert Quality Analysis
Identify which alerts lead to successful trades vs. false signals
Real-Time Monitoring
- Live Activity Feed: See alerts as they're processed
- System Health: Monitor API connections and delivery channels
- Alert Queue: Track processing delays and backlogs
- Error Tracking: Immediate notification of system issues
Plan Limits & Subscription Tiers
Understand the limits and features available with each Chirpify plan.
Plan Comparison
๐ฏ Alert Builder - $15/month
Limits
- 5 alert groups maximum
- 10 chirps per day
- Basic rate limiting options
- 1 delivery channel per group
Features
- โ Telegram integration
- โ Basic analytics dashboard
- โ Alert sequences
- โ Time-based filtering
- โ Exchange trading
- โ Custom webhooks
โก Signal Amplifier - $25/month
Limits
- 10 alert groups maximum
- 30 chirps per day
- Advanced rate limiting
- 3 delivery channels per group
Features
- โ All Alert Builder features
- โ Custom webhooks
- โ Email notifications
- โ Advanced analytics
- โ Alert group nesting
- โ Exchange trading
๐ Chirpify Elite - $49/month
Limits
- Unlimited alert groups
- Unlimited chirps per day
- All rate limiting options
- Unlimited delivery channels
Features
- โ All previous plan features
- โ Crypto exchange trading
- โ Portfolio management
- โ API access
- โ Priority support
- โ Advanced risk management
Usage Monitoring
Track your usage against plan limits:
- Daily Chirp Count: Monitor chirps sent vs. daily limit
- Alert Group Usage: See how many groups you're using
- Feature Access: Identify which features require plan upgrades
- Historical Usage: Review past usage patterns for plan optimization
Plan Upgrade Benefits
๐ Mid-cycle Upgrades
Upgrade anytime with prorated billing - get immediate access to higher limits
๐ Usage Alerts
Get notified when approaching plan limits to avoid service interruption
๐ฏ Optimization Recommendations
Receive suggestions for optimal plan selection based on your usage patterns
Troubleshooting Guide
Common issues and their solutions to keep your Chirpify system running smoothly.
Alert Processing Issues
๐ซ Alerts Not Triggering
Symptoms:
- Expected alerts not being delivered
- Alert groups showing as inactive
- No activity in logs despite TradingView alerts
Diagnosis Steps:
- Check alert group status (active/paused)
- Verify webhook URL in TradingView matches exactly
- Review filter conditions for overly restrictive rules
- Check if within rate limiting window
- Verify time-based conditions (market hours, silence periods)
โก Delayed Alert Processing
Symptoms:
- Alerts arrive minutes after TradingView trigger
- Inconsistent processing times
- Alerts arriving out of order
Solutions:
- Check system status page for outages
- Verify TradingView webhook delivery times
- Review rate limiting settings
- Consider upgrading plan for higher priority processing
Delivery Channel Problems
๐ฑ Telegram Delivery Issues
Common Problems:
- Bot not responding: Check bot token validity
- Messages not in group: Verify bot admin permissions
- Wrong chat ID: Re-fetch chat ID after bot setup
- Rate limited: Telegram limits 30 messages/second per bot
๐ฐ Exchange Trading Issues
Common Problems:
- Orders not executing: Check API key permissions
- Insufficient balance: Verify account funding
- Invalid symbols: Confirm symbol format matches exchange
- Position sizing errors: Review position size calculation settings
๐ Webhook Delivery Issues
Common Problems:
- Endpoint unreachable: Verify webhook URL accessibility
- Authentication failures: Check webhook authentication settings
- Payload format errors: Verify receiving endpoint expects correct format
- Timeout issues: Ensure webhook endpoint responds within 10 seconds
Performance Optimization
๐ Speed Optimization
- Use simple filter conditions when possible
- Avoid overly complex nested logic
- Set appropriate rate limits to prevent overload
- Use time windows to batch similar alerts
๐ Resource Optimization
- Archive inactive alert groups
- Clean up old webhook configurations
- Review and optimize filter logic regularly
- Monitor usage against plan limits
Getting Support
๐ Emergency Contact
For critical issues affecting live trading:
- Email: support@chirpify.app (mark as URGENT)
- Status Page: status.chirpify.dev
- Twitter: @ChirpifySupport for real-time updates