Actions99
- Group Accounts Actions
- Group Account Codes Actions
- Accounts Actions
- Expenses 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
- Cards Actions
- Suppliers Actions
- Fund Accounts 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 the accounting or procurement 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. The output does not include binary data.
Dependencies
- Requires an API key credential or similar authentication token configured in n8n to authorize requests to the external supplier management API.
- The base URL for the API must be set in the node credentials or environment variables.
- The node depends on an OpenAPI-based client library for request construction and response parsing.
Troubleshooting
- Missing or invalid Account Id: The operation requires a valid account identifier; ensure this property is correctly set.
- Authentication errors: Verify that the API key or authentication token is properly configured and has sufficient permissions.
- Network or API errors: Check connectivity and API endpoint availability. Review error messages for HTTP status codes indicating issues like rate limiting or invalid payloads.
- Unexpected response structure: If the output JSON does not match expectations, confirm that the API version and schema have not changed.
Links and References
- Refer to the external supplier management API documentation for detailed information on required fields and response formats.
- Consult n8n documentation on setting up API credentials and using OpenAPI integrations.