List vendors
Read selected vendor directory metadata across checked pages.
Connector library
Bill connector.
Read BILL vendor and customer directory metadata through four named v3 actions with managed developer/session credentials, fixed sandbox/production origins and bounded pagination.
Connector download
Download Bill
Versioned ZIP for your CXFabric tenant.
Use this connector in a flow
- Register the ZIP in your tenant, or add a new version if the connector is already installed.
- Create or select a credential if the action requires one.
- In a Draft flow, add an available action, choose its version, connect it, and map inputs.
- Test the step and flow; review output and failures before activation.
See readme.md in the ZIP for settings and limitations.
- Version
v0.2.0.0 Choose version
- Release
- 2026-10-04
- Package
- Implemented source
- Schema credentials
- Basic auth
- Connection settings
- Environment
- Package size
- 10 KB
- SHA-256
939d560b67e8df0d97851999182163e13ded7d23b8b920ba382dcd97879942be
Version history
What's new
- v0.2.0.0Latest · 2026-10-04 · Implemented source
Read BILL vendor and customer directory metadata through four named v3 actions with managed developer/session credentials, fixed sandbox/production origins and bounded pagination.
- v0.1.1.0Earlier · 2026-10-02 · Starter scaffold
Historical readable HTTP scaffold.
Included in this version
Included actions
Implemented in v0.2.0.0. Use a separate flow trigger; no webhook trigger is included.
Get vendor
Read selected metadata for one exact vendor ID.
List customers
Read selected customer directory metadata across checked pages.
Get customer
Read selected metadata for one exact customer ID.
Vendor API
API and access
Implementation considerations
- Vendor lookups: List vendors or look up selected metadata by an exact BILL vendor ID.
- Customer lookups: List customers or look up selected metadata by an exact BILL customer ID.
- Bounded directory reads: Read selected names, archived state and currency codes with checked pagination.
- Use scheduled flows for directory reads; no webhook trigger is included.
- Use a managed Basic Auth credential as a two-secret container: issued developer key in username and its issued organization API session ID in password. Requests send devKey and sessionId headers.
- Select sandbox or production to match the issued session and developer key. Login, MFA and session renewal remain outside this package.
- The v3 package reads selected directory metadata. Contact, banking, account-number and payment data and payment processing are outside its scope.
Related connectors
More in Commerce, Finance & Operations APIs
Support
Need help with Bill?
Tell us what you need to connect or change.