Airtable - automate recurring tasks
Hello there!
This is a supporting workflow for an Airtable Base that handles Recurring Tasks. The objective of the workflow is to handle creating tasks on a recurring basis depending on the Airtable Setup
You can access that Airtable Template here for complete context- Airtable Universe
The functionality of the workflow can be easliy adapted to any data source. Feel free to contact us with any doubts or questions at http://sidetool.co β Use this as is, or adapted to your existing Airtable Base β embrace automated simplicity! ππ
Airtable - Automate Recurring Tasks
This n8n workflow automates the creation of recurring tasks in Airtable and notifies a Slack channel about these new tasks. It's designed to streamline task management for operations that require regular, scheduled actions.
What it does
This workflow simplifies the process of managing recurring tasks by:
- Triggering on a schedule: It listens for a scheduled event (e.g., daily, weekly) to check for tasks that are due to recur.
- Fetching recurring tasks from Airtable: It queries a specified Airtable base and table to find tasks marked as recurring.
- Processing task data: It uses a Code node to transform and prepare the data for the new task entry, potentially calculating new due dates or other relevant fields based on the recurring logic.
- Creating new tasks in Airtable: It adds a new record to the Airtable table for each recurring task that needs to be generated.
- Notifying Slack: It sends a message to a designated Slack channel, informing the team about the newly created recurring tasks.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n instance: A running instance of n8n.
- Airtable Account: An Airtable account with a base and table set up to manage your tasks. This table should include fields relevant to recurring tasks (e.g., task name, recurrence interval, last completed date, next due date).
- Slack Account: A Slack workspace and a channel where you want to receive notifications.
Setup/Usage
- Import the workflow:
- Copy the provided JSON code.
- In your n8n instance, click "New" in the workflows section.
- Click the "Import from JSON" button and paste the copied JSON.
- Configure Credentials:
- Airtable: Set up your Airtable credential by providing your API Key and Base ID. Ensure the Airtable nodes are configured to use this credential and point to the correct Base ID and Table Name.
- Slack: Set up your Slack credential by providing your Bot User OAuth Token. Configure the Slack node to use this credential and specify the Channel ID where messages should be posted.
- Configure Airtable Trigger:
- Open the "Airtable Trigger" node.
- Select your Airtable credential.
- Specify the "Base ID" and "Table Name" where your recurring tasks are stored.
- Configure the "Trigger When" setting to match how you determine a task is due for recurrence (e.g., a specific view, a filter formula).
- Configure Airtable (Read) Node:
- Open the "Airtable" node (the one after the trigger).
- Ensure it uses the correct Airtable credential, Base ID, and Table Name.
- Adjust the "Filter By Formula" or "View" to retrieve only the tasks that are currently due to be recurred.
- Configure Edit Fields (Set) Node:
- Customize this node to set the appropriate fields for the new recurring task. This might involve:
- Setting a new
Next Due Datebased on the recurrence interval. - Clearing
Completed Dateor other status fields. - Copying the
Task NameorDescription.
- Setting a new
- Customize this node to set the appropriate fields for the new recurring task. This might involve:
- Configure Code Node:
- This node is crucial for the recurrence logic. Edit the JavaScript code to implement your specific recurrence rules. For example, if a task recurs weekly, the code should calculate the
Next Due Dateto be one week from the current date or the previousNext Due Date.
- This node is crucial for the recurrence logic. Edit the JavaScript code to implement your specific recurrence rules. For example, if a task recurs weekly, the code should calculate the
- Configure Airtable (Write) Node:
- Open the second "Airtable" node (the one for creating new records).
- Ensure it uses the correct Airtable credential, Base ID, and Table Name.
- Map the fields from the previous nodes to create the new Airtable record correctly.
- Configure Slack Node:
- Open the "Slack" node.
- Select your Slack credential.
- Specify the "Channel" where you want the notifications to appear.
- Customize the "Text" field to create a meaningful message about the newly created recurring tasks. You can use expressions to include task details.
- Activate the workflow: Once all configurations are complete, activate the workflow. It will now run according to its schedule and automate your recurring tasks.
Related Templates
Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax
Spark your creativity instantly in any chatβturn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. π What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing π§ Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation π Required Credentials OpenAI API Setup Go to platform.openai.com β API keys (sidebar) Click "Create new secret key" β Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai β Dashboard β API Keys Generate a new API key β Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) βοΈ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflowβchat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" π― Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration β οΈ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions
Automate Dutch Public Procurement Data Collection with TenderNed
TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch π LinkedIn β Wessel Bulte
π How to transform unstructured email data into structured format with AI agent
This workflow automates the process of extracting structured, usable information from unstructured email messages across multiple platforms. It connects directly to Gmail, Outlook, and IMAP accounts, retrieves incoming emails, and sends their content to an AI-powered parsing agent built on OpenAI GPT models. The AI agent analyzes each email, identifies relevant details, and returns a clean JSON structure containing key fields: From β senderβs email address To β recipientβs email address Subject β email subject line Summary β short AI-generated summary of the email body The extracted information is then automatically inserted into an n8n Data Table, creating a structured database of email metadata and summaries ready for indexing, reporting, or integration with other tools. --- Key Benefits β Full Automation: Eliminates manual reading and data entry from incoming emails. β Multi-Source Integration: Handles data from different email providers seamlessly. β AI-Driven Accuracy: Uses advanced language models to interpret complex or unformatted content. β Structured Storage: Creates a standardized, query-ready dataset from previously unstructured text. β Time Efficiency: Processes emails in real time, improving productivity and response speed. *β Scalability: Easily extendable to handle additional sources or extract more data fields. --- How it works This workflow automates the transformation of unstructured email data into a structured, queryable format. It operates through a series of connected steps: Email Triggering: The workflow is initiated by one of three different email triggers (Gmail, Microsoft Outlook, or a generic IMAP account), which constantly monitor for new incoming emails. AI-Powered Parsing & Structuring: When a new email is detected, its raw, unstructured content is passed to a central "Parsing Agent." This agent uses a specified OpenAI language model to intelligently analyze the email text. Data Extraction & Standardization: Following a predefined system prompt, the AI agent extracts key information from the email, such as the sender, recipient, subject, and a generated summary. It then forces the output into a strict JSON structure using a "Structured Output Parser" node, ensuring data consistency. Data Storage: Finally, the clean, structured data (the from, to, subject, and summarize fields) is inserted as a new row into a specified n8n Data Table, creating a searchable and reportable database of email information. --- Set up steps To implement this workflow, follow these configuration steps: Prepare the Data Table: Create a new Data Table within n8n. Define the columns with the following names and string type: From, To, Subject, and Summary. Configure Email Credentials: Set up the credential connections for the email services you wish to use (Gmail OAuth2, Microsoft Outlook OAuth2, and/or IMAP). Ensure the accounts have the necessary permissions to read emails. Configure AI Model Credentials: Set up the OpenAI API credential with a valid API key. The workflow is configured to use the model, but this can be changed in the respective nodes if needed. Connect the Nodes: The workflow canvas is already correctly wired. Visually confirm that the email triggers are connected to the "Parsing Agent," which is connected to the "Insert row" (Data Table) node. Also, ensure the "OpenAI Chat Model" and "Structured Output Parser" are connected to the "Parsing Agent" as its AI model and output parser, respectively. Activate the Workflow: Save the workflow and toggle the "Active" switch to ON. The triggers will begin polling for new emails according to their schedule (e.g., every minute), and the automation will start processing incoming messages. --- Need help customizing? Contact me for consulting and support or add me on Linkedin.