Document the Update invoice details step in the Chargebee guide - #463
Merged
Conversation
Adds a "Writing values back to Chargebee" section covering the new chargebee.update.details step, which writes workflow-resolved values (e.g. the Polish KSeF number) back onto the originating Chargebee invoice as custom fields — or, for credit notes, as a comment. Includes configuration guidance (field/value table, expr expressions over the GOBL envelope, the head.stamps lookup for the KSeF number), a JSON example, placement notes, and two screenshots. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Adds documentation to the Chargebee guide for the new Update invoice details workflow step (chargebee.update.details), explaining how to write values produced during a workflow back onto the originating Chargebee invoice/credit note, including a KSeF example and supporting screenshots.
Changes:
- New “Writing values back to Chargebee” section in
guides/chargebee.mdxdescribing behavior (invoice vs. credit note), configuration, an expr example, and step placement guidance. - Adds screenshots showing the step configuration UI and the resulting custom field on a Chargebee invoice.
Reviewed changes
Copilot reviewed 1 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| guides/chargebee.mdx | Documents the new “Update invoice details” step, including configuration details, expr examples, and JSON sample. |
| assets/guides/cb_update_invoice_details.png | Screenshot referenced by the new section showing step configuration. |
| assets/guides/cb_updated_custom_field.png | Screenshot referenced by the new section showing the populated custom field result in Chargebee. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Documents the new Update invoice details step (
chargebee.update.details) in the Chargebee guide.The step writes values produced during a workflow back onto the originating Chargebee document — today as custom fields via Chargebee's
update_detailsendpoint, and as a comment for credit notes (which Chargebee can't update). The motivating use case is recording a tax authority's reference number, such as the Polish KSeF number, into a Chargebee custom field.Changes
guides/chargebee.mdx, covering:find(head.stamps, …)lookup used for the KSeF number)assets/guides/: the step config panel and the populated custom field on a Chargebee invoice.Notes
find(head.stamps, {.prv == "favat-ksef-number"}).val(the value lives inhead.stamps, notdoc.ext).cb-*template.🤖 Generated with Claude Code