Quick overview
Quick overview This workflow runs hourly to sync project records from a Microsoft SQL Server staging table into matching Asana projects, updating Asana custom fields and writing back sync status, errors, and the Asana project ID to the database. How it works Runs every hour and queries Microsoft SQL Server for up to 100 project records that are not yet synced (or previously failed) and have fewer than three sync attempts. Marks each selected record as “Processing” in SQL Server to prevent duplicate handling during the sync. Calls the Asana API to list projects in a specific portfolio and matches the SQL ProjectName to an Asana project name. If no Asana project matches, updates the SQL record to a “Waiting for Project ID” state with a message for manual project creation. If a match is found, retrieves the Asana project’s custom fields and builds an update payload mapping SQL values (manager, margin, revenue, costs, and dates) to Asana custom fields. Updates the Asana project via the Asana API and then marks the SQL record as “Completed” with the Asana project ID, or logs the error and marks the record as “Failed” while incrementing the attempt counter. Setup Create Microsoft SQL Server credentials in n8n and ensure the Projects_Asana_Staging table (and columns like SyncedToAsana, SyncAttempts, LastSyncDate, LastSyncError, and AsanaProjectID) exists and matches the queries. Provide an Asana personal access token and set the ASANA_PAT and ASANA_PORTFOLIO_GID workflow variables to a portfolio that contains the projects you want to sync. Ensure the target Asana projects have custom fields with the expected names (for example, “Project Manager”, “Actual Margin”, “Revenue”, and the onsite dates) so the workflow can map and update them. Review the hourly schedule and adjust the interval, record limit, or retry threshold in the SQL query if needed for your environment. An n8n automation workflow template by n8n Lab.
n8n Lab
web
free
Others in the same category, ranked by how often they are opened.
