Woocommerce new order => create invoice ninja Invoice

Describe the problem/error/question

I’m currently working on establishing a workflow between WooCommerce and Invoice Ninja, but I’m encountering a couple of challenges. I’d appreciate any guidance or tips you can provide.

  1. Issue with Triggering Workflow from WooCommerce: My workflow is supposed to start when a new order is created in WooCommerce. However, no matter what I’ve tried, n8n does not seem to recognize the new order created in WooCommerce. I’ve attempted various approaches, but the issue persists. Any suggestions on how to troubleshoot or resolve this would be greatly appreciated.
  2. Integrating Invoice Ninja with Contact ID Requirement: For creating a new invoice in Invoice Ninja, it requires a contact ID. Previously, when I used platforms like Make (Integromat) or Zapier, I implemented a ‘Filter’ to match the WooCommerce order email with the existing contacts in Invoice Ninja. This process involved checking if there’s a contact with the same email address in Invoice Ninja. If a match was found, the corresponding ID was used to create the new invoice. If not, a new contact was created in Invoice Ninja, and this new ID was used for the invoice. I’m unsure how to replicate this process in n8n. Could anyone share insights or a workflow example on how to achieve this?

Thank you in advance for your help. I’m looking forward to your suggestions and solutions!

What is the error message (if any)?

  1. waiting for you to creat an event in Woocommerce doesn’t stop even event(order) is created
  2. contact ID is recommended to create invoice

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)
{
  "meta": {
    "instanceId": "33c54ae3525572ce39cdb2b16d7a65d6f4ccd917385e652024313599cc50f370"
  },
  "nodes": [
    {
      "parameters": {
        "event": "order.created"
      },
      "id": "7fc58c0b-de07-4006-90a4-3d2dc93fa4c0",
      "name": "WooCommerce Trigger",
      "type": "n8n-nodes-base.wooCommerceTrigger",
      "typeVersion": 1,
      "position": [
        580,
        300
      ],
      "webhookId": "11c3c1b2-fe8d-4df8-9529-f707abfe7038",
      "credentials": {
        "wooCommerceApi": {
          "id": "5L1Yfm2YNNScjOVW",
          "name": "WooCommerce account"
        }
      }
    }
  ],
  "connections": {},
  "pinData": {}
}

{
  "meta": {
    "instanceId": "33c54ae3525572ce39cdb2b16d7a65d6f4ccd917385e652024313599cc50f370"
  },
  "nodes": [
    {
      "parameters": {
        "resource": "invoice",
        "additionalFields": {}
      },
      "id": "de671568-5066-4299-8c0b-7b9d8dc69632",
      "name": "Invoice Ninja",
      "type": "n8n-nodes-base.invoiceNinja",
      "typeVersion": 2,
      "position": [
        800,
        300
      ],
      "credentials": {
        "invoiceNinjaApi": {
          "id": "w08pFWuMRVavog1o",
          "name": "Invoice Ninja account"
        }
      }
    }
  ],
  "connections": {},
  "pinData": {}
}

Share the output returned by the last node

Information on your n8n setup

  • 1.20.0
  • Docker
  • not sure, but since I do not get a trigger it will not start
  • Docker
  • Ubuntu

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:

Hi @discrockers, welcome to the community and sorry for the trouble.

Let’s look at one problem at a time. Seeing even the trigger part seems to fail, can you check your WooCommerce webhook logs here to verify what happened to the data WooCommerce has (or should have) sent to n8n? Are there any webhooks sent? If so, which response did they see?

If webhooks were sent and have received a success response from n8n, can you confirm whether you have your workflow is active and whether you are storing execution data? If so, you would need to check the execution list to see what has happened, as production executions would not show up on your canvas in real-time.