The flow
Starts it 1Logic 6Service 8
The steps in the order they run, from what starts it.
- 1Hourly Schedule TriggerSchedule triggerStarts it
- 2Query Unsynced ProjectsMicrosoft SqlService
- 3Any Records to Sync?FilterLogic
- 4Mark as ProcessingMicrosoft SqlService
- 5Pass Project ContextCodeLogic
- 6Get Portfolio Projects from AsanaHttp RequestService
- 7Match Project by NameCodeLogic
- 8Project Found in Asana?IfLogic
- 9Get Project Custom FieldsHttp RequestService
- 10SQL, Mark Waiting for Project IDMicrosoft SqlService
- 11Build Custom Fields PayloadCodeLogic
- 12Update Asana Project FieldsHttp RequestService
- 13SQL, Mark Project CompletedMicrosoft SqlService
- 14Handle Project Update ErrorCodeLogic
- 15SQL, Mark Project FailedMicrosoft SqlService
How it's built
- Starts on
- A clock
- Steps
- 15, with 1 branch
- Size
- Medium: a working afternoon
- Connects to
- Nothing by connector; it calls services over plain HTTP
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account. You connect your own accounts after importing it; none are included.
What starts it?
It starts on a clock.
Does it use AI?
No. Every step is fixed logic or a call to a service, so it does the same thing every time.
How long does it take to set up?
Plan an afternoon. 15 steps is enough that you should read each one before running it.
How do I import it?
Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.
Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 15 steps before you point it at anything that matters.