📄️ Actions
Action events in Ductape are used to interact with APIs and services, both internal and external. They enable your feature to perform operations such as creating, retrieving, updating, or deleting resources by making API calls or invoking service actions.
📄️ Notifications
Notification events in Ductape are used to communicate important information to users or systems through channels such as push notifications, emails, or webhooks. They enable your feature to notify stakeholders, ensuring that essential updates and messages are delivered effectively.
📄️ Database Actions
Database Action events in Ductape are used to execute operations on your database, such as creating, reading, updating, or deleting records. They enable your feature to interact directly with your database, supporting robust data processing and error handling.
📄️ Jobs
Job events in Ductape are scheduled tasks designed to execute at specified intervals or at a specific point in time. They are ideal for running autonomous, isolated tasks such as notifications, database cleanup, report generation, or data synchronization.
📄️ Features
A Feature event in Ductape allows you to invoke another feature as a subroutine within an event sequence. This enables modular, reusable workflows and helps you compose complex logic by chaining features together.
📄️ Storage
Storage events in Ductape are used to handle file or blob storage operations, such as uploading files to cloud storage providers (AWS S3, GCP, Azure, etc.). They enable your feature to store, retrieve, or process files as part of an event sequence.
📄️ Fallbacks
Fallback events in Ductape enable resilient workflows by automatically switching to backup providers if the primary one fails. Unlike manual fallback logic, you simply define the input for the event, and Ductape handles provider selection and failover behind the scenes.
📄️ Quotas
Quota events in Ductape are used to enforce usage limits and track consumption of resources or features within your product. They help prevent overuse, manage rate limits, and ensure fair access to services by defining and checking quotas as part of your workflow.