Frequently Asked Questions
What is DotPortion, and who is it for?
What is DotPortion, and who is it for?
- Startup founders
- Backend & full-stack developers
- Internal tooling teams
- Product teams building APIs without boilerplate
How does DotPortion differ from tools like Postman, n8n, or backend frameworks?
How does DotPortion differ from tools like Postman, n8n, or backend frameworks?
- Unlike Postman, DotPortion creates and hosts APIs
- Unlike traditional frameworks, you don’t write boilerplate code
- Unlike automation tools, workflows are request-driven APIs, not cron jobs
- Request parameters
- Business logic
- Database operations
- Authentication
- Response formatting
What is a workflow in DotPortion?
What is a workflow in DotPortion?
- Starts with an API trigger
- Passes data through connected nodes
- Executes nodes sequentially or conditionally
- Returns a structured HTTP response
What are nodes, and how do they work?
What are nodes, and how do they work?
Each node performs a single responsibility, such as:
- Reading request parameters
- Running logic or conditions
- Querying a database
- Generating JWTs
- Formatting responses
Can I write custom logic or code inside DotPortion?
Can I write custom logic or code inside DotPortion?
- Runs in a secure sandbox
- No access to the underlying system
- Ideal for transformations, validations, and calculations
How is data passed between nodes?
How is data passed between nodes?
- The request
- Previous nodes’ outputs
Does DotPortion support databases?
Does DotPortion support databases?
- Secure credential management
- Dynamic queries
- Read & write operations
How does authentication work?
How does authentication work?
- API keys
- JWT generation & validation
- Custom auth logic using nodes
Is version control supported?
Is version control supported?
- Track changes
- Roll back to previous versions
- Maintain staging and production flows
How are workflows deployed?
How are workflows deployed?
- You deploy it with a single click
- DotPortion provisions and hosts the API
- Each deployment gets a stable endpoint
What happens if a workflow fails during execution?
What happens if a workflow fails during execution?
- Execution stops immediately
- Errors are logged with node-level details
- You can inspect inputs, outputs, and failure reasons
How do I debug workflows?
How do I debug workflows?
- Step-by-step execution logs
- Node-level input/output inspection
- Error tracing for failed executions
Is user data stored or used for training AI models?
Is user data stored or used for training AI models?
- API request data is not used for training
- Execution data is retained only for debugging and logs
- Credentials are securely encrypted
Where is DotPortion hosted?
Where is DotPortion hosted?
Are there rate limits?
Are there rate limits?
How do I report bugs or issues?
How do I report bugs or issues?
- Share details in the community
- Include workflow screenshots or JSON
- Mention the node where it occurred
How do I request new features or nodes?
How do I request new features or nodes?
- New nodes
- Integrations
- Execution improvements
- UI/UX enhancements
Does DotPortion guarantee uptime or SLAs?
Does DotPortion guarantee uptime or SLAs?
I have a question that isn’t listed here
I have a question that isn’t listed here