N8n-nodes-fedex: tracking, rating, shipping, and address validation

Built with n8n
, , , , , ,
1

Hey all :waving_hand:

Sharing a community node I just published: n8n-nodes-fedex.

I kept hitting the same wall on shipping workflows. There was no clean FedEx node, so you end up hand-rolling the OAuth2 flow inside HTTP Request nodes and fighting 401s before you can even pull a tracking number. This wraps all of that up in a clean node.

What it does right now:

  • Track by number (real-time status and scan events)
  • Get rate quotes for a shipment (negotiated and list rates)
  • Create a shipment and pull back the label + tracking number
  • Validate and standardize an address

Token retrieval and refresh are handled inside the credential, nothing reads from env vars or files, so it follows the community node rules. Zero runtime dependencies, plain REST through n8n’s built-in helpers.

Repo + install info: n8n-fedex-node/README.md at main · nodrel-dev/n8n-fedex-node · GitHub
npm link: https://www.npmjs.com/package/@nodrel-dev/n8n-nodes-fedex

It covers the standard FedEx operations cleanly. If you run it and hit a carrier edge case it doesn’t handle yet, open an issue with your n8n version and the operation you were running and I’ll take a look!

Would love feedback from anyone doing logistics workflows on the user experience and config setup within the node UI itself; it’s live in n8n as of yesterday. UPS and a select few of Canadian carriers are next :canada:

1 Like
2

Handling the OAuth2 token flow inside the credential is the right call - that’s the part that trips people up the most with FedEx. A natural companion workflow for this would be: on new order in a Shopify/WooCommerce webhook, run the Rate node to pick the cheapest qualifying service, create the shipment, then watch the tracking status on a schedule and push updates to a Slack or email notification. That’s probably the most common FedEx automation pattern people need in practice.

1 Like