Updated Feb 02, 2026

How to Schedule Time-Based Actions in Adalo

Table of Contents

Adalo lets you automate app workflows based on dates and times, simplifying tasks like sending reminders or updating user statuses. With tools like Conditional Actions and Custom Actions, you can trigger events based on specific time rules (e.g., "Is after", "Is before"). Here's what you need to know:

Triggers and Actions: Triggers (e.g., button clicks) start workflows, while actions (e.g., notifications) define what happens next.
Built-In vs. Custom Actions: Built-in triggers handle basics like navigation or database updates. Custom Actions (Professional Plan required) connect your app to external tools like Zapier or SendGrid.
Setting Time-Based Triggers: Use conditional logic tied to Date/Time properties to automate workflows (e.g., send a notification if today's date matches a condition).
Testing and Publishing: Test workflows in Adalo's preview mode and adjust conditions for reliability. Monitor live workflows through Adalo's database and analytics.

Adalo supports time-sensitive features across web, iOS, and Android, offering flexibility for apps like booking systems or reminder tools. Start with the free plan and scale as needed.

Scheduling Notifications in Adalo: Holiday Building Series - Part 3

Adalo

What You Need Before Getting Started

Before diving into scheduled workflows, make sure your account and database are ready. Start by testing basic features on the free tier, but you’ll need to upgrade to the Professional Plan to access Custom Actions. These are essential for working with external workflows and API connections. Custom Actions apply at the team level, so any edits will automatically update across all your apps. This is especially useful when integrating with external calendars like Google or Outlook.

Your database is the backbone of any scheduled action. To set up effective triggers, create a well-structured collection, such as "Events" or "Content Posts." Include properties like Date & Time, Status (e.g., Draft, Scheduled, Published), and, if needed, Time Zone. For apps requiring precise scheduling, add a Time Slots collection and a Buffer Time (measured in minutes) to avoid overlaps. If your app involves multiple users, link scheduled items to the Users collection for tailored actions.

Adding a Time Zone property ensures that scheduled content displays correctly in each user’s local time. When using Magic Text for dates in external integrations, select the "No Formatting" option to ensure the data processes smoothly.

One thing to keep in mind: Adalo user login sessions expire after 20 days by default, which could impact notifications. To avoid issues, always include a fallback action in your conditional logic. This ensures your app stays functional even if time-based conditions aren’t met. With this solid foundation, your app will be ready for reliable performance.

Next, you’ll learn how to define triggers and actions in Adalo to make your scheduled workflows work seamlessly.

How to Define Triggers and Actions in Adalo

Understanding Triggers and Actions

In Adalo, triggers are the "when" and actions are the "what" of your app's workflows. A trigger, like a button tap, form submission, or image click, kicks off an action, which tells your app how to respond. Actions create the interactive experience by connecting visual components to your database properties.

For more flexibility, you can add conditional logic to actions. Go to the "Show Advanced" settings and change "When does this happen?" from "Always" to "Sometimes." This allows you to set specific rules, such as sending a reminder email only if the event date "Is after" today or falls "Between" two dates.

Adalo also uses Magic Text and Arguments to pass dynamic data - like user inputs or screen details - into your actions.

Using Built-In Triggers

Built-in triggers handle common app functions without needing external tools. These include Link actions for screen navigation, Create/Update/Delete Record for managing database entries, and Sign Up/Log In for user authentication. These triggers are available on all Adalo plans and work seamlessly with your app's internal collections.

For workflows based on time or conditions, you can pair built-in triggers with conditional logic. For example, you might update a record's status only if today's date meets a specific condition. Here's a tip: if you're using multiple conditional Link Actions on one component, always include a fallback non-conditional action. This ensures users won't get stuck without a destination if none of the conditions are met.

Building Custom Actions

When built-in triggers aren't enough, Custom Actions let you connect your app to external services, opening up new possibilities. However, this feature is only available on the Professional Plan or higher.

Use Custom Actions to integrate with tools like SendGrid for email, Zapier for automation, or calendar APIs for scheduling. To create one, select a component, click "New Custom Action", and follow these steps:

Name your Custom Action and choose an action type (Create, Update, or Delete).
Enter the API Base URL and method (e.g., POST).
Add any required authentication headers (like Authorization Bearer tokens).
Define inputs for dynamic data, such as Text, Number, or Date/Time.
Use Magic Text to build the JSON request body with your inputs.
Test the connection to ensure everything works.

Keep in mind that Custom Actions are saved at the team level. If you edit one that's used in multiple apps, the changes will apply everywhere. To avoid disrupting other projects, create separate Custom Actions for each app. Lastly, when working with dates in API URLs, set Magic Text formatting to "No Formatting" so external services can interpret the data correctly.

How to Configure Time-Based Triggers and Workflows

Scheduling Actions Step-by-Step

To set up time-based actions in Adalo, use conditional logic tied to Date/Time properties. Start by selecting the component - like a button or form - that will serve as the trigger. Add the action you want, such as updating a record or sending a notification. Then, click "Show Advanced" and change the "When does this happen?" setting from "Always" to "Sometimes".

From there, pick a Date/Time property in your database and choose a comparison type. You have three options:

"Is after": Triggers the action once a specific time has passed.
"Is before": Executes the action before a set deadline.
"Is between": Creates a time window for the action to occur.

For tasks that need to repeat, you can integrate external automation tools through Custom Actions (available with the Professional Plan). When passing Date/Time data to these external services, set Magic Text formatting to "No Formatting" to ensure compatibility .

Now, let’s explore how these triggers work with other app features.

Connecting Time-Based Triggers with Other App Features

After scheduling your actions, you can enhance workflows by combining these triggers with Adalo’s built-in features. Use conditional date logic alongside Change Data actions to automatically update records or pair it with Trigger Notification actions to send alerts at specific times.

To ensure notifications work effectively, confirm that recipients have been active within the last 14 days and have granted notification permissions. Add a "Request Notification Permission" action early in your app flow to handle this. For native apps on iOS or Android, assign a "Target Screen" where users will land when they tap the notification.

You can also create calendar-based features by using a "Link to Website" action. Add a formatted URL with Date/Time parameters from your database, allowing users to add events to their calendars. For instance, include &reminder=30 to set a 30-minute advance reminder.

Tips for Optimizing Scheduled Workflows

When creating workflows with multiple time conditions, always include a fallback action that isn’t conditional. This ensures users have a clear path forward if none of the conditions are met.

Keep in mind that users cannot receive notifications they’ve triggered themselves. Notifications are designed to alert other users or to be initiated by system-level events.

Testing and Publishing Your Scheduled Actions

How to Test Scheduled Actions in Adalo

Before launching your app, use Adalo's Preview button to test scheduled workflows on iPhone, Android, and desktop views. This ensures that your conditional logic and time-based triggers work seamlessly across different devices.

For workflows that span longer durations, you can simulate shorter intervals. For example, to test a 30-minute timer, adjust the duration to 30–60 seconds using the formula (Current Time – Start Time) × 86400 minus 1800 seconds.

Leverage the X-Ray feature to pinpoint any performance issues before publishing. If your workflows interact with external APIs, such as calendar integrations, use the "Run Test Request" button in the Custom Action setup. This step helps confirm that JSON responses and data mapping are functioning as expected.

It's also a good idea to create multiple test accounts to cover a variety of user scenarios. For workflows involving notifications, test push notifications on native or PWA builds (since they’re inactive in web preview). Ensure recipients meet the criteria - like being active in the last 14 days and granting notification permissions.

Once you’ve verified that everything works as intended, you’re ready to publish your scheduled actions.

Publishing and Monitoring Your Actions

Publishing your app follows Adalo's usual deployment process. For web apps, set up your URL or custom subdomain through the Publish panel for an instant launch. For native apps, prepare the necessary assets and follow the app store submission guidelines.

After going live, keep an eye on your scheduled actions by reviewing your database. Check properties like "Status" (e.g., Pending, Confirmed, Completed) or flags like "Reminder Sent" (True/False) to confirm that workflows are running as expected. For workflows managed by external tools like Zapier or Make, review their task history and logs to troubleshoot any issues.

Adalo's Analytics tab can also provide useful insights. Track visitor activity, download stats, and user locations to evaluate how well your workflows perform in a live environment. These monitoring steps help ensure the reliability and effectiveness of your scheduled actions.

Conclusion

With Adalo, scheduling time-based actions becomes a seamless part of your app-building process. Whether it's sending reminders, updating statuses, or triggering workflows, these features let your app handle tasks automatically - no manual effort required. By leveraging conditional logic alongside date and time properties, you can craft experiences that align with user schedules and business demands.

Adalo’s single-codebase approach ensures these workflows function consistently across web, iOS, and Android. Time-sensitive operations run smoothly, backed by a reliable platform that manages scheduling data directly in its built-in database. For more advanced automation, Custom Actions provide the flexibility to extend your app’s capabilities.

Start testing your scheduling features on Adalo's Free Plan, and as your app evolves, upgrade to access additional tools. To ensure everything runs as intended, use buffer times to avoid overlapping events and test thoroughly across various time zones for a seamless experience for all users.

FAQs

What are the advantages of using Custom Actions in Adalo?

Custom Actions in Adalo open the door to extending your app's functionality and crafting solutions tailored to your needs. With these, you can connect to external services and APIs, enabling advanced tasks like pulling in external data or triggering workflows that go beyond the platform's standard offerings.

They also simplify automation, enhancing both the user experience and your app's efficiency. Think about setting up automatic notifications, updating data in real time, or integrating with third-party tools - all without writing a single line of code. These tools make it simple to build apps that are dynamic and specifically designed to meet your unique requirements.

How do I make sure scheduled actions in Adalo work properly across time zones?

To make sure scheduled actions in Adalo work seamlessly across various time zones, always store date and time data in the date/time format. This approach automatically accounts for time zone differences, helping to avoid inconsistencies.

When configuring scheduled actions, take the user's local time zone into account to prevent unexpected time shifts. It's important to thoroughly test your setup to verify that actions trigger at the right local time for every user. Using a consistent date and time format helps reduce potential issues and ensures dependable functionality across time zones.

What should I do if a scheduled action in Adalo isn’t working as expected?

If a scheduled action in Adalo isn’t working as expected, start by taking a closer look at your workflow setup. Check that the trigger conditions are set up correctly and align with the timing you’ve planned. Also, verify that any conditional logic is properly configured and tied to the scheduled action.

Next, ensure your app has the required permissions, and confirm that any connected services, like notifications, are properly authorized and configured. Testing the workflow under various scenarios can help you narrow down the issue - adjust one setting at a time to see what might be causing the problem.

Still stuck? Make sure your app is running the latest version and review any platform updates or outages that could be affecting its performance. If the problem continues, consult Adalo’s troubleshooting guides or contact their support team for additional help.