What are the Platform default limits?
Discover how Flexito's platform limits and point system can be tailored to your needs, ensuring seamless integration and efficient automation. Whether you're managing complex workflows or utilising various integrations, understanding these limits can help you optimise your operat
Listen to an audio overview
A short, AI-generated podcast-style summary of this article.
On this page
Discover how Flexito's platform limits and point system can be tailored to your needs, ensuring seamless integration and efficient automation. Whether you're managing complex workflows or utilising various integrations, understanding these limits can help you optimise your operations effectively.
Here are the default platform limits. Some limits can be increased with a connected paid add-on.
Topic | Limit |
|---|---|
Max execution time | 40 seconds |
Max Steps error | 30 Steps |
Max Step Points | 80 points |
Default timeout for external request | 15 seconds |
Default timeout for OpenAI action | 30 seconds |
Flexito OmniAI Native Object Storage Limit | 1 Gb |
Max Total Nodes | 2000 |
Smart Delays | 50 per bot user per 24 hours. smart delays 10 seconds or less are not counted to this total |
Max Inbound Webhooks Requests | 500 per 24 hours |
Max OpenAI Embeddings | 500 |
Flexito OmniAI API Requests | 1000 per hour |
Googlesheet filter limit | Up till 5000th entry |
Googlesheet API limit | 3 requests per second |
Broadcast error rate limits | No more than 100 errors within 5 mins |
Chat history across all channels(send from user) | 6 months |
Chat history across all channels (send from live chat agent) | 6 months |
Chat history across all channels(send from bot) | 3 months |
Max file upload size limits | 10MB |
Media file size storage limits | 100MB(free plan); 1GB(paid plan) |
WhatsApp Media File Expire date | For meta cloud api, it’s 30 days by default; If you have connected S3 storage in the integration, the expire date is the same as the chat history. |
Total Date/Time triggers | 50 per bot |
Add-on Options
We offer an add-on option to increase these limits, costing $39 per month for each bot. Note that this is applied at the bot level, not the workspace level.
For every $39 per month, you can increase the following limits:
Max points increase by 10 points.
Max steps increase by 10 steps.
Max timeout limits increase by 10 seconds.
External request timeout increase by 10 seconds.
OpenAI action timeout increase by 10 seconds.
Users can choose which limits to increase and arrange payment here:
Understanding the Point Counting System
Actions That Do Not Count Points
The following actions do not count towards points: setting or clearing custom fields, JSON operations, adding or removing tags, conditions, randomisers, and 'Goto' actions.
Actions That Count as 5 Points
These actions are worth 5 points each: sending messages, typing/waiting actions, external requests, mini app actions, triggering or scheduling workflows, Google Sheets actions, data store actions, firing triggers, and notifications (voice, SMS, WhatsApp, Slack, Telegram, live chat, email), as well as updating user profiles.
Integration Actions (1 Point Currently, Increasing to 5 Points on 1st August 2025)
The following integration actions currently count as 1 point each, but will increase to 5 points from 1st August 2025: Shopify, WooCommerce, Calendly, Cloudinary, S3 storage, Stripe, Facebook API, WhatsApp, Google API, Google Maps, Mapbox, Eleven Labs, eCommerce API, Store Location API, SSO API, SMS Blacklist API, Bot User API, Ticket API, Rate Limit API, GoHighLevel API (v1), OpenAI, Gemini, Coze, Deepseek, AI_Task, Dialogflow, and others.
Actions That Count as 10 Points
These actions count as 10 points each: adding team notes, using Smart Delay, and executing JavaScript functions.
All other actions and nodes are considered 1 point each.
If a user reaches 80 points without any user interaction (such as a question node), the bot will stop.
Maximum 30 Steps Error
Nodes are counted, and you can have multiple actions in one node. However, within 30 nodes, there must be at least one question node, or the bot will stop.
Maximum 40 Seconds Timeout Error
If a flow runs continuously for 40 seconds without user interaction (like a question block), this error will occur.
This error typically happens when many external requests or OpenAI actions are used. If the destination server is slow, it may cause a 40-second timeout, stopping the bot automation.
By default, our external request timeout is set to 15 seconds, and our native OpenAI action timeout is 30 seconds.