LogoLogo
  • Docs
  • Connector Configuration
  • Knowledge Base
  • Changelog
  • Get Started
  • The Basics
    • What is Appmixer
    • Appmixer interfaces
      • Appmixer Studio
      • Backoffice
      • SDK Demo
  • Appmixer Studio features
    • What is a flow
    • Creating a flow
    • Sharing a flow
    • Flow examples
      • Forward customer support calls based on PIN
      • Feed customer data to Mailchimp
      • Google Drive document approvals
      • CSV import: calculate average value
    • Creating an Integration template
    • Using Variables to map data
    • Using Modifiers to alter data
    • Implementing logic
    • Troubleshooting errors
    • Visual features
      • Selecting multiple objects
      • Copying objects
      • Zooming in/out
      • Exporting a flow to an Image
      • Renaming a flow
      • Renaming a component
    • Utility modules
      • Webhooks
      • HTTP
      • Filters
      • Scheduling
      • Forms
      • Tasks
      • Language
    • Connected accounts
      • Connecting a new account
      • Managing accounts
    • Data storage
      • Creating a Data storage
      • Editing a Data storage
      • Using Data storage in a flow
    • Insights
      • Logs
      • Dashboard
      • Charts
      • Chart types
      • Data aggregations
    • Changing a password
  • Backoffice features
    • Insights
    • Flows
    • Users
    • Access Control List
    • Services
    • Extra: Creating custom components
  • SDK Demo
    • SDK Demo: Workflow automation
    • SDK Demo: Integration templates
Powered by GitBook
On this page

Was this helpful?

Export as PDF
  1. Appmixer Studio features
  2. Utility modules

Scheduling

PreviousFiltersNextForms

Last updated 3 years ago

Was this helpful?

. In this section, we'll show you a simple yet effective way to implement Scheduling features into your flows.

Imagine we want to get a daily notification based on the current weather. In the flow below, we look at cloudiness and, based on the current weather, send either a "Cloudy" or "Sunny" email.

Notice how we've used the "Timer" component (named "Every day" and located at the beginning of the flow) to run the flow every 24 hours (1440 minutes).

You may have noticed, we used the "Timers" module that consist of three components: Scheduler, Timer and Wait.

Here is a simple explanation of each of the "Timers" components.

Timer This trigger fires at the frequency provided by the interval configuration property. First message is sent to output when flow is started, this message does not have lastTick' and 'elapsed' property set.

Wait This component receives a message and waits for provided time (interval) to send original message to output port.

Keep in mind that you can customise all components and also implement your own using NodeJS and upload them to the Appmixer engine via the API to suit your specific business needs.

Note that you could as well use the Scheduler component which provides a more flexible configuration when it comes to scheduling. The Scheduler component uses the cron syntax. Learn more here:

Scheduler This trigger schedules jobs to run periodically at fixed times, dates, or intervals using the .

Having learned the basics about the Scheduling feature, .

https://en.wikipedia.org/wiki/Cron
cron syntax
let's look at another great tool, Forms
Previously, you learned about the power of Webhooks and HTTP requests
Using the "Timer" component in a flow
Scheduler, Timer and Wait components