Actions99
- Expenses Actions
- Group Accounts Actions
- Group Account Codes Actions
- Accounts Actions
- Purchase Orders Actions
- Get A List Of Purchase Orders
- Create A New Purchase Order
- Get A Purchase Order
- Update A Purchase Order
- Open A Purchase Order
- Get A List Of Purchase Orders Items For A Specific Purchase Order
- Create A Purchase Order Item
- Get A Purchase Order Item
- Update A Purchase Order Item
- Delete A Purchase Order Item
- Get A List Of Goods Received Notes For A Specific Purchase Order
- Create A Goods Received Note
- Attach A File To A Goods Received Note
- Delete A Goods Received Note
- Suppliers Actions
- Fund Accounts Actions
- Cards Actions
- Expense Categories Actions
- Tax Rates Actions
- Amortizations Actions
- Account Teams Actions
- Account Codes Actions
- External Teams Actions
- Custom Fields Actions
- Get Custom Fields
- Create A New Custom Field
- Get Custom Field
- Update Custom Field
- Delete A Custom Field And All Its Values
- Get Custom Field Values
- Create A Custom Field Value
- Delete Custom Field Values
- Get A Custom Field Value
- Update A Custom Field Value
- Delete A Custom Field Value
- Get Managers For A Specific Custom Field Value
- Adds Managers For A Specific Custom Field Value
- Replaces Managers For A Specific Custom Field Value
- Removes Managers For A Specific Custom Field Value
- Webhook Subscriptions Actions
- Group Teams Actions
Overview
This node operation creates a new supplier in an external system by sending the necessary supplier data to the API. It is useful for automating supplier management workflows, such as adding new vendors or partners directly from your automation without manual entry. For example, when onboarding a new supplier, this node can be used to programmatically register their details into your procurement or accounting system.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account to which the new supplier will be linked |
Output
The node outputs JSON data representing the newly created supplier record as returned by the external API. This typically includes the supplier's unique identifier, status, and any other metadata provided by the service after creation. The output does not include binary data.
Dependencies
- Requires an API key credential for authenticating requests to the external supplier management API.
- The base URL for the API must be configured in the node credentials or environment variables.
- The node depends on an OpenAPI specification internally to define its operations and properties.
Troubleshooting
- Missing or invalid Account Id: The operation requires a valid account identifier. Ensure that the "Account Id" property is correctly set and corresponds to an existing account in the target system.
- Authentication errors: If the API key or authentication token is missing or incorrect, the node will fail to create the supplier. Verify that the API credentials are properly configured.
- API connectivity issues: Network problems or incorrect base URL configuration can cause request failures. Confirm the API endpoint is reachable and correctly set.
- Unexpected API response: If the external API changes or returns errors, check the response message for clues and update the node configuration accordingly.
Links and References
- Refer to the external supplier management API documentation for detailed information on required fields and response structure.
- Consult n8n documentation on how to configure API credentials and use OpenAPI-based nodes.