Automation library · E-commerce

Sync SAP sales order tasks between Microsoft SQL Server and Asana

Started by a clock. It calls services over plain HTTP rather than through connectors. 29 steps, 3 branches: large, and worth reading before you trust it with anything live.

Large

29 stepsLarge: read it before trusting it with anything live
3Branches: places the flow splits
0Loops or waits
0Services by connector: it calls them over plain HTTP

The flow

Starts it 1Logic 13Service 15

The steps in the order they run, from what starts it.

  1. 1Every 10 MinutesSchedule triggerStarts it
  2. 2Query Unsynced Sales OrdersMicrosoft SqlService
  3. 3Any Sales Orders to Sync?FilterLogic
  4. 4Mark SO as ProcessingMicrosoft SqlService
  5. 5Pass SO ContextCodeLogic
  6. 6Look Up Asana Project GID from SQLMicrosoft SqlService
  7. 7Merge SO + Project GIDCodeLogic
  8. 8Asana Project Exists?IfLogic
  9. 9Get Project SectionsHttp RequestService
  10. 10SQL, Mark SO Waiting for ProjectMicrosoft SqlService
  11. 11Find Target Section by DocTypeCodeLogic
  12. 12Handle SO Sync ErrorCodeLogic
  13. 13Route by ChangeTypeSwitchLogic
  14. 14SQL, Mark SO FailedMicrosoft SqlService
  15. 15Search Existing Tasks in SectionHttp RequestService
  16. 16Build UPDATE PayloadCodeLogic
  17. 17Delete Asana TaskHttp RequestService
  18. 18Check if Task Already ExistsCodeLogic
  19. 19Update Existing Asana TaskHttp RequestService
  20. 20SQL, Mark DELETE CompletedMicrosoft SqlService
  21. 21Task Already Exists?IfLogic
  22. 22SQL, Mark UPDATE CompletedMicrosoft SqlService
  23. 23Build Payload for Duplicate Task UpdateCodeLogic
  24. 24Build Task Custom Fields PayloadCodeLogic
  25. 25Update Duplicate TaskHttp RequestService
  26. 26Create Asana TaskHttp RequestService
  27. 27SQL, Mark Duplicate Update CompletedMicrosoft SqlService
  28. 28Extract Created Task GIDCodeLogic
  29. 29SQL, Mark INSERT CompletedMicrosoft SqlService

How it's built

Starts on
A clock
Steps
29, with 3 branches
Size
Large: read it before trusting it with anything live
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?

Take your time. At 29 steps it is large: read it before trusting it with anything live.

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.

Before you run it

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 29 steps before you point it at anything that matters.