Integrations
Set up Invoice Ninja credentials in Duaer
Store Invoice Ninja connection details in Duaer for digital-organization nodes to use at runtime. Secrets are protected by the instance encryption key and are not written into node parameters.
Create an Invoice Ninja API token
The Duaer Invoice Ninja API credential:
- v5: in Invoice Ninja, open Settings > Account Management > API Tokens, create a token, and put it in API Token. v4: create it under Settings > API Tokens.
- URL: https://invoicing.co for hosted v5, https://app.invoiceninja.com for hosted v4, or your own address when self-hosted.
- Secret is optional; fill it in only if you set an API secret in v5.
API Version in the Invoice Ninja node must match your instance version.
Invoice Ninja API fields in Duaer
In Duaer, choose Invoice Ninja API when you create a credential, then fill in these fields:
- URL: Default URL for v4 is https://app.invoiceninja.com, for v5 it is https://invoicing.co.
- API Token (secret)
- Secret (secret): This is optional, enter only if you did set a secret in your app and only if you are using v5.
When you save, Duaer tests the connection with these values.
Duaer nodes that use it: Invoice Ninja, Invoice Ninja Trigger.
Save the connection in Duaer
Open Credentials and create Invoice Ninja. Fill in the key, OAuth, or server fields. After you save, digital-organization nodes reference this credential instead of putting the secret in a parameter.
Credential values are protected by the instance encryption key. If you change or lose that key, stored credentials cannot be decrypted. See the hosting notes on encryption keys. The matching node is under the related node.
Who can use this credential
Who can see or edit it follows projects and roles. Do not paste secrets into chat or variables. External vaults are covered under external secrets.
Questions
Do Invoice Ninja secret values appear in Duaer node parameters?
No. In Duaer, Invoice Ninja secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.
What usually stops a Invoice Ninja credential from saving in Duaer?
Wrong fields, an OAuth callback that does not match the instance URL, or a role that cannot create credentials. Check the fields Invoice Ninja expects, then confirm you can create credentials in that project.
In this section
Built-in integrations in Duaer
Built-in triggers, actions, and credentials in Duaer. Triggers start a workflow. Actions run a step after it has started.
IntegrationsRisks of community nodes in Duaer
Before you install a community node in Duaer, know the code comes from a source the instance admin trusts, and know what permissions it gets.
IntegrationsTroubleshoot community nodes in Duaer
When a Duaer community node will not install or run, check the version, permissions, and node docs, then the instance logs.
IntegrationsMake custom API calls for an app in Duaer
When a Duaer app node does not expose the API you need, use HTTP Request and reuse that app’s saved authentication.
IntegrationsIntegrations in Duaer
Built-in triggers, actions, and credentials in Duaer. Community nodes are extra packages. Custom operations reuse saved authentication with HTTP Request.
CredentialsBuilt-in credentials in Duaer
Per-service credential notes for Duaer built-ins. The create flow is in the credentials overview; node docs link to the matching service page.
Create nodesCreate a custom node for Duaer
Write a node package for Duaer when built-in nodes and custom operations are not enough and you will reuse the step.