Bill v2

Provides integration with BILL, an accounts payable, accounts receivable, and business-payments platform used to manage vendors, bills, and related finance records through REST APIs.

The Flowgear BILL Node lets you query, create, update, and delete supported BILL resources by selecting template-driven operations from the curated v3 API surface.

Revision History

0.0.0.5 - Initial release.
0.0.0.7 - Removed page handling properties from templates.
0.0.0.8 - Aligned the Runtime connector contract.
0.1.0.0 - Completed the Runtime overhaul with eager first-request startup and lazy continuation.
0.1.0.1 - Added the OpenAPI runtime dependency required to load templates.
0.1.1.0 - Updated the OpenAPI contract, split templates by HTTP verb, and added sanitized mutation request echoes.
0.1.1.1 - Preserved inherited fields in designer templates when OpenAPI schemas use constraints-only allOf overlays.
0.1.1.5 - Updated the production BILL API endpoint.

Connection

Use the Connection to store your BILL authentication and environment settings. Username, Password, Organization ID, and Developer Key are required.

Property Type Description
Is Sandbox Boolean Set to true for sandbox credentials and endpoints. The default is false.
Username String BILL API username.
Password Masked BILL API password.
Organization ID String BILL organization identifier.
Developer Key Masked BILL developer key.
Token Masked BILL session token returned from authentication.

Setup Notes

The Username and Password are the credentials you use to sign in to your BILL environment.

  1. Sign in to your BILL environment.
  2. Open Settings from the left pane.
  3. In the left pane, expand Sync & Integrations, then click Manage Developer Keys.
  4. In the new pane, click Generate developer key in the top-right corner.
  5. Accept the terms, then click Generate key.
  6. Open the new entry and reveal the Developer Key, then save that value.
  7. Copy the Organization ID shown at the bottom of the Developer Keys pane.
  8. Enter the Username, Password, Developer Key, and Organization ID values in the Flowgear Connection setup screen.
  9. Do not enter the Token. Flowgear generates it automatically.
  10. Click Test to confirm that the Connection is configured correctly.

Methods

Use these Methods to retrieve, create, update, and delete BILL resources through the available OpenAPI operations.

Query

Retrieves BILL resources.

The Node handles paging internally for Query operations and emits the returned business rows directly.

Parameter Type Description
Connection Connection Connection information for BILL.
OperationId String Identifier of the OpenAPI operation to execute.
Options Object Additional parameters such as route and query values.
Return Type Description
Response Array Response payload objects returned by the operation. Query rows contain the BILL business payload only. A no-match result returns zero rows. If the first provider request fails, Flowgear surfaces that BILL error instead of returning an empty result.

Create

Creates BILL resources.

Parameter Type Description
Connection Connection Connection information for BILL.
OperationId String Identifier of the OpenAPI operation to execute.
Options Object Additional parameters such as route and query values.
Items Array Optional request-body items for the create operation.
Return Type Description
Response Array Response payload objects returned by the operation. Mutation rows include the provider payload together with Flowgear.IsSuccess, Flowgear.Message, and Flowgear.Request. Provider status-like fields are surfaced as providerStatus, providerStatusMessage, and providerErrorMessage.

Update

Updates BILL resources.

Parameter Type Description
Connection Connection Connection information for BILL.
OperationId String Identifier of the OpenAPI operation to execute.
Options Object Additional parameters such as route and query values.
Items Array Optional request-body items for the update operation.
Return Type Description
Response Array Response payload objects returned by the operation. Mutation rows include the provider payload together with Flowgear.IsSuccess, Flowgear.Message, and Flowgear.Request. Provider status-like fields are surfaced as providerStatus, providerStatusMessage, and providerErrorMessage.

Delete

Deletes BILL resources.

Parameter Type Description
Connection Connection Connection information for BILL.
OperationId String Identifier of the OpenAPI operation to execute.
Options Object Additional parameters such as route and query values.
Items Array Optional request-body items for the delete operation.
Return Type Description
Response Array Response payload objects returned by the operation. Delete rows include the provider payload together with Flowgear.IsSuccess, Flowgear.Message, and Flowgear.Request. Provider status-like fields are surfaced as providerStatus, providerStatusMessage, and providerErrorMessage.

Usage Notes

  • Use Options to pass route and query values required by the selected OperationId.
  • Each Method accepts only operations that match its HTTP verb: Query uses GET operations, Create uses POST operations, Update uses PATCH or PUT operations, and Delete uses DELETE operations.
  • The Node handles BILL paging for Query, so you do not pass page, nextPage, or prevPage in Options. When max is not supplied, the Node requests 100 rows per page.
  • Mutation request echoes in Flowgear.Request use the current Items object, or Options for bodyless operations. Nested Content values are excluded.
  • Query retrieves the first BILL page when the step runs. Additional pages are fetched only as the Workflow consumes the response stream.
  • Create, Update, and Delete send the first input item when the step runs. Later items are processed as the Workflow consumes the response stream, and an empty connected input sends no request to BILL.