Skip to content

Launch via a schedule

Schedule recurring process launches

Prerequisites

  • A Tallyfy account with the right permissions
  • Process templates ready for scheduled launch
  • Access to middleware platforms (like Zapier, Make.com) or API capabilities
  • Your schedule needs (daily, weekly, monthly)

Benefits

Automatic launches run repeating workflows (daily, weekly, monthly) on time without manual intervention.

Implementation options

1. Middleware platforms

Schedule through Zapier, Make.com, or Microsoft Power Automate.

Implementation steps:

  1. Sign up for your chosen middleware platform.
  2. Connect it to your Tallyfy account.
  3. Create a new workflow/scenario with a schedule trigger.
  4. Set the schedule (time, day, frequency).
  5. Add a Tallyfy action to launch a specific process.
  6. Set the process name format and fill any required fields.
  7. Test and turn on the scheduled launch.

Example: Daily equipment check

Trigger: Schedule (Every day at 8:00 AM)
Action: [Launch](/products/pro/launching/) Tallyfy [process](/products/pro/tracking-and-tasks/processes/)
Template: Equipment Safety Check
Process name: Equipment Check - {date}

2. API-based scheduling

Build custom solutions using the Tallyfy API with server-side schedulers.

Implementation steps:

  1. Write a server-side script that calls the Tallyfy API.
  2. Set up the script to launch specific process templates.
  3. Set up a task scheduler (like cron job, Windows Task Scheduler).
  4. Schedule the script to run at the desired times.
  5. Add logging and error handling.
  6. Test thoroughly.

Example: Node.js script

const cron = require('node-cron');
const axios = require('axios');
// Schedule task to run at 9:00 AM every Monday
cron.schedule('0 9 * * 1', async () => {
try {
await axios.post('https://go.tallyfy.com/api/processes', {
template_id: 'your-template-id',
name: `Weekly Report - ${new Date().toLocaleDateString()}`
}, {
headers: {
'Authorization': 'Bearer YOUR_API_TOKEN',
'Content-Type': 'application/json'
}
});
console.log('Weekly report process launched successfully');
} catch (error) {
console.error('Failed to launch process:', error);
}
});

3. Integrated workflows

Trigger from existing systems (ERP, HRIS) that already have scheduling capabilities.

Implementation steps:

  1. Identify scheduling systems already used (ERP, HRIS, etc.).
  2. Set up integration points between these systems and Tallyfy.
  3. Trigger based on scheduled events in those systems.
  4. Map data from the source system to Tallyfy process fields.
  5. Test the integration thoroughly.

Middleware schedulers are the simplest solution. See our Monthly Process Launch with Zapier guide for a detailed example.

Common use cases

Process TypeFrequencyExample Implementation
Compliance auditsMonthlySchedule equipment inspection process on the 1st of each month
Financial reportingWeeklyLaunch expense approval workflow every Friday at 4:00 PM
Team updatesDailyTrigger daily standup checklist each morning at 9:00 AM
Maintenance checksQuarterlySchedule facility inspection process on the first day of each quarter
Client reviewsAnnuallyLaunch client satisfaction survey process on client anniversary dates

Launching > Launch on a schedule

Tallyfy processes can be automatically scheduled using middleware tools like Zapier by setting up a schedule trigger that launches specific process templates at predetermined intervals without manual intervention.

Zapier > Automate monthly process launch with Zapier

Tallyfy processes can be automatically launched monthly using Zapier’s scheduler trigger which connects to the Launch Process action allowing businesses to set up recurring workflows that run on the first day of each month without manual intervention.

Triggers > Launch via middleware

Middleware platforms enable automatic launching of Tallyfy workflows by connecting external applications as triggers and seamlessly transferring data between systems without requiring manual intervention or custom coding.

Launching > Triggers

Tallyfy offers seven flexible process launch triggers including manual buttons API calls email triggers magic links scheduled automation task completion chains and kick-off forms to accommodate different organizational needs and technical capabilities while enabling automatic data pre-population for seamless workflow initiation.