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
- 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 when automating supplier management workflows, such as adding new suppliers from form submissions or integrating with procurement systems. For example, you can use this node to automatically add a supplier when a new vendor signs up on your platform.
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 details such as the supplier's unique ID, name, and other metadata assigned by the system upon 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 provided and correctly formatted.
- 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 set up.
- API connectivity issues: Network problems or incorrect base URL configuration can cause request failures. Confirm the API endpoint is reachable and correctly configured.
- Unexpected API response: If the API returns an error or unexpected data structure, check the API documentation and ensure all required fields are included.
Links and References
- Refer to the external supplier management API documentation for detailed information on creating suppliers.
- n8n documentation on how to configure API credentials and use custom nodes.