budget-monitoring-variance-payload-builder

To build a budget variance payload for Lark securely, this skill converts your budget and actual records into Lark interactive-card payloads using a NyxID service, replacing the need for direct Lark API credentials. It handles four specific record types to construct the final payload.

The best way to automate budget monitoring flows through NyxID is using the service runner mode, which fetches your records through the NyxID proxy, builds the interactive-card payload, and sends the Lark card directly to your chat without manual credential management.

Yes, you can visualize budget and actual records as a Lark card using NyxID. The skill processes four distinct record types—coreBudgetRecords, coreActualRecords, aelfBudgetRecords, and aelfActualRecords—and deterministically converts them into an interactive Lark card payload.

To start building a Lark budget variance payload, run the skill with an input JSON containing your coreBudgetRecords, coreActualRecords, aelfBudgetRecords, and aelfActualRecords. The skill processes this data structure to generate the deterministic Lark interactive-card payload.

No, you do not need direct Lark API credentials to send budget variance cards. The skill utilizes a NyxID service proxy to handle both data fetching and the final Lark card delivery, ensuring secure and credential-free communication for your monitoring workflow.