Log Airtable worklogs to Tempo with Jira and Slack notifications
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 10 nodes and runs on a schedule (every day at 23:00). Along the way it connects Airtable, Slack and Jira Software. It also calls api.tempo.io over HTTP.
How it runs
Trigger: On a schedule (every day at 23:00).
- FetchDailyWorklog (Airtable): search
- JiraIssueConvert (Jira Software): get
- DataMapping (Edit Fields (Set)): sets 5 fields: id, fields.date, fields.startTime…
- PrepareTempoPayload (Code): runs custom JavaScript code
- TempoUpload (HTTP Request): calls api.tempo.io (POST)
- RecordHistory (Airtable): create
- DailyTableClear (Airtable): delete record
- Aggregate: combines items into one
- Slack: uses Slack
Services it uses
HTTP calls to: api.tempo.io
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (8)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Airtable
n8n-nodes-base.airtable - Edit Fields (Set)
n8n-nodes-base.set - HTTP Request
n8n-nodes-base.httpRequest - Slack
n8n-nodes-base.slack - Aggregate
n8n-nodes-base.aggregate - Jira Software
n8n-nodes-base.jira - Code
n8n-nodes-base.code
From the author
Quick overview This workflow runs nightly to pull time entries from Airtable, converts Jira issue keys to issue IDs, logs the time to Tempo via its REST API, archives the processed entries back to Airtable, and sends a confirmation message to a Slack user.…