Connect with n8n

Open your n8n workflow

Create a new workflow (or open an existing one). Add whatever trigger makes sense for your use case — a Schedule trigger, a webhook from another app, or a manual trigger while you test.

Add an HTTP Request node for "Create route"

1. Click + to add a new node, then search for and select HTTP Request.
2. In the node settings, set the following:
   • Method: POST
   • URL: https://teamapi.upperinc.com/api/v1/ext-create-route
3. Under Authentication, choose Generic Credential Type → Header Auth.
   • Set Name to x-api-token.
   • Set Value to your Upper Crew API token (paste the value you copied from Settings → Webhooks).
4. Set Body Content Type to JSON.
5. Under Body, add your JSON payload. A minimal example that creates a named route:

{
  "route_name": "Morning Deliveries",
  "route_date": "2026-06-30",
  "optimize_for": "time",
  "units": "miles",
  "service_time": 120
}

6. Click Test step to run the node. A successful call returns:

{
  "code": 200,
  "message": "Route created successfully.",
  "data": {
    "route_id": 18452,
    "route_name": "Morning Deliveries",
    "route_date": "2026-06-30",
    "optimize_for": "Time",
    "service_time": 120,
    "units": "Miles",
    "pickup_settings": "Auto"
  }
}

Note the route_id in data — you will need it in the next node.

Add a second HTTP Request node for "Optimize route"

1. Connect a second HTTP Request node to the output of the first.
2. Configure it:
   • Method: POST
   • URL: https://teamapi.upperinc.com/api/v1/ext-optimize-route
   • Same Header Auth credential (x-api-token) as above.
   • Body Content Type: JSON.
3. In the body, reference the route_id returned by the previous node using an n8n expression:

{
  "route_id": {{ $node["HTTP Request"].json.data.route_id }},
  "timezone": "America/New_York"
}

4. Click Test step. A successful call returns a pending status with a queue_id:

{
  "code": 200,
  "message": "Optimization started successfully.",
  "data": {
    "route_id": 18452,
    "status": "pending",
    "queue_id": "6657f1a2b9d3c40012ab34cd"
  }
}

Optimization runs asynchronously. To check when it finishes, add a further HTTP Request node calling GET https://teamapi.upperinc.com/api/v1/ext-optimization-status?route_id=18452 and poll it (or wait a fixed interval) until data.status returns "optimized". See Routes for the full ext-optimization-status reference.

Activate and test the full workflow

Once both nodes run cleanly in test mode, click Save and then Activate to turn the workflow on. Subsequent trigger events will now create and optimize routes in Upper automatically.

Add a Webhook node to your n8n workflow

1. In a new (or existing) n8n workflow, click + and add a Webhook node as the trigger.
2. Set HTTP Method to POST.
3. Set Authentication to None (Upper sends the payload directly; you can add IP filtering or a secret in a subsequent node if needed).
4. Copy the Production Webhook URL shown in the node panel. It looks like:

https://your-n8n-instance.example.com/webhook/abc123xyz

Register the URL in Upper Crew

1. In the Upper web app, open Settings → Webhooks.
2. Paste the n8n production webhook URL into the receiver URL field.
3. Save.

Upper will now POST event notifications to that URL whenever a relevant event occurs in your account (for example, a stop is updated or a route is completed). Each delivery attempt is also recorded in the delivery history on that same Settings screen. See Webhooks for more detail on managing webhook URLs and reviewing history.

Handle the incoming payload in your workflow

After the Webhook node, add any downstream nodes to act on the data Upper sends — for example:

• An If node to branch on event type.
• A Set node to map Upper fields to your own schema.
• A Send Email, Slack, or database node to notify your team or persist the data.

Test the end-to-end flow

In n8n, click Listen for test event on the Webhook node, then trigger a real event in Upper (for example, update a stop). n8n will capture one delivery so you can inspect the payload shape and build your downstream logic before activating the workflow for production.