Description
Overview
This accountability notification workflow monitors physical activity daily and triggers email alerts when activity falls below a predefined threshold. This automation workflow is designed for individuals seeking structured oversight of their exercise routines by involving an accountability team to maintain motivation.
The workflow uses a time-based cron trigger at 11:00 AM and connects to the Strava API via OAuth2 credentials to retrieve all recent activity data. It deterministically compares moving time against a 30-minute threshold to decide further actions.
Key Benefits
- Automated daily checks ensure consistent monitoring of physical activity without manual input.
- Integration with Strava API provides real-time activity data for accurate evaluation.
- Threshold-based conditional logic triggers notifications only when activity falls short.
- Email alerts engage an accountability team, promoting support and encouragement.
- Configurable parameters allow customization of activity thresholds and contact recipients.
Product Overview
This accountability notification workflow initiates via a cron node triggering at 11:00 AM daily. Upon activation, it sets configurable parameters including a moving time threshold of 1800 seconds (30 minutes), user identification, and accountability partner emails. Using OAuth2 credentials, the Strava node fetches all recent user activities without limitation.
The core logic applies an If node to compare the most recent activity’s moving time against the predetermined threshold. If the moving time meets or exceeds the threshold, the workflow halts gracefully via a no-operation node. If below threshold, the workflow proceeds to send an email alert to three accountability partners using SMTP authentication. The email content is dynamically generated with user-specific information to prompt encouragement.
Error handling relies on platform defaults; no custom retry or backoff is configured. Data processing is transient—no persistence beyond runtime. This workflow supports deterministic daily evaluation of physical activity and proactive engagement of support contacts.
Features and Outcomes
Core Automation
This accountability notification automation workflow inputs daily trigger events, evaluates moving time against a 30-minute threshold, and routes execution based on conditional logic. The key decision node (“Check Activity Level”) uses a numeric comparison to branch flow deterministically.
- Single-pass evaluation of activity data for timely decision making.
- Defined threshold ensures consistent criteria for notification triggers.
- Deterministic branching minimizes false alerts and unnecessary notifications.
Integrations and Intake
The orchestration pipeline integrates directly with the Strava API using OAuth2 credentials for secure data access. It retrieves comprehensive activity records with no imposed limits. Input parameters are set internally via a Set node before API call.
- Strava API for activity data retrieval via OAuth2 authentication.
- Cron scheduler provides time-based triggers for regular workflow execution.
- SMTP email service for sending alerts to multiple accountability partners.
Outputs and Consumption
The workflow’s output is an email notification sent asynchronously when activity thresholds are not met. The message includes user and contact details populated dynamically from workflow variables.
- Email dispatch to predefined accountability partners with contextual user information.
- Conditional output ensuring alerts are sent only when necessary.
- Non-persistent, transient data handling minimizes storage footprint.
Workflow — End-to-End Execution
Step 1: Trigger
The workflow initiates daily at 11:00 AM via a cron node configured for a fixed schedule. This time-based trigger ensures automated, regular execution without manual intervention.
Step 2: Processing
Following the trigger, the workflow sets constant parameters including minimum moving time and accountability partner emails through a Set node. It then invokes the Strava node to retrieve all recent user activities using OAuth2 authentication. Basic presence checks confirm the existence of moving time data in the retrieved activity.
Step 3: Analysis
The workflow performs a numeric comparison between the user’s latest activity moving time and the defined threshold of 1800 seconds. This If node branches execution deterministically: if the moving time is greater or equal, the workflow terminates; if less, it proceeds to notify partners.
Step 4: Delivery
When activity is below threshold, an email node sends a message to three preconfigured accountability partners. The email originates from the user’s email address and contains a templated message encouraging accountability. The dispatch uses SMTP credentials for secure delivery.
Use Cases
Scenario 1
A user wants to maintain daily physical activity but struggles with motivation. This workflow automatically monitors their Strava data and alerts a support team if daily activity falls below 30 minutes. The result is timely encouragement from peers, promoting consistent exercise habits.
Scenario 2
Fitness coaches managing multiple clients need a scalable method to track client activity. This automation workflow fetches all recent activities and flags clients not meeting minimum moving time, sending notifications to accountability partners. It enables proactive client engagement without manual tracking.
Scenario 3
Health researchers require automated data-driven alerts based on participant activity thresholds. This workflow aggregates daily moving time data, applies a 30-minute threshold, and triggers email alerts to a designated team. The deterministic output supports structured participant monitoring.
How to use
Import the workflow into your n8n environment and configure OAuth2 credentials for Strava API access. Update the Set node with your name, email, accountability partner emails, and desired minimum moving time in seconds. Ensure SMTP credentials are configured to enable email sending. Activate the workflow to run daily at 11:00 AM. Expect automatic evaluation of your recent Strava activities and email notifications sent to your accountability contacts if movement thresholds are not met.
Comparison — Manual Process vs. Automation Workflow
| Attribute | Manual/Alternative | This Workflow |
|---|---|---|
| Steps required | Multiple manual checks and email composition daily | Single automated daily execution with conditional branching |
| Consistency | Variable due to human error and forgetfulness | Deterministic, scheduled evaluation with fixed thresholds |
| Scalability | Limited by manual effort and monitoring capacity | Scales automatically with no additional overhead |
| Maintenance | Requires continual manual monitoring and follow-up | Low maintenance; updates only needed for credentials or parameters |
Technical Specifications
| Environment | n8n automation platform |
|---|---|
| Tools / APIs | Strava API (OAuth2), SMTP email service, Cron scheduler |
| Execution Model | Time-triggered, asynchronous with conditional branching |
| Input Formats | None externally; internal JSON parameters and Strava API JSON response |
| Output Formats | SMTP email messages |
| Data Handling | Transient processing, no data persistence |
| Known Constraints | Relies on daily availability of Strava API and SMTP service |
| Credentials | Strava OAuth2, SMTP authentication |
Implementation Requirements
- Valid Strava OAuth2 credentials for API access
- Configured SMTP credentials for email dispatch
- Network access to Strava API endpoints and SMTP server
Configuration & Validation
- Set the minimum moving time and accountability partner emails in the Set node parameters.
- Verify Strava OAuth2 credentials by testing API connectivity within n8n.
- Confirm SMTP credentials by sending a test email through the Email Send node.
Data Provenance
- Trigger node: Cron node scheduled daily at 11:00 AM
- Data source: Strava node retrieving all recent activities with OAuth2 authentication
- Conditional logic: If node comparing “moving_time” field against 1800 seconds threshold
FAQ
How is the accountability notification automation workflow triggered?
The workflow is triggered daily at 11:00 AM by a cron node configured within n8n, enabling automated, time-based evaluations.
Which tools or models does the orchestration pipeline use?
The pipeline integrates with the Strava API using OAuth2 for activity data retrieval and an SMTP email node for notifications. It applies conditional logic via an If node for threshold evaluation.
What does the response look like for client consumption?
When activity is below threshold, the workflow sends an email to the accountability team containing the user’s name and a message encouraging increased activity.
Is any data persisted by the workflow?
No data is persisted permanently. Processing is transient, with activity data retrieved and evaluated at runtime only.
How are errors handled in this integration flow?
Error handling relies on n8n’s platform defaults; no custom retry, backoff, or error branches are configured in this workflow.
Conclusion
This accountability notification workflow provides automated daily monitoring of physical activity by integrating Strava data with conditional evaluation and email alerts. It ensures deterministic assessment against a configurable moving time threshold and notifies a support team when activity is insufficient. The workflow’s operation depends on the availability of both the Strava API and an SMTP email service for delivery. It offers a repeatable, low-maintenance solution for structured accountability without data persistence or manual intervention.
Reviews
There are no reviews yet.