lark-onboarding-email-approval-payload-builder

Create Lark approval instance payloads from onboarding event data.

Updated May 4, 2026
One-click install
npx skills add https://github.com/ChronoAIProject/nyx-skills --skill lark-onboarding-email-approval-payload-builder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lark-onboarding-email-approval-payload-builder
Source: https://github.com/ChronoAIProject/nyx-skills/tree/main/lark-onboarding-email-approval-payload-builder
Command: npx skills add https://github.com/ChronoAIProject/nyx-skills --skill lark-onboarding-email-approval-payload-builder

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Streamlines the process of building approval payloads for onboarding new Lark users by automatically extracting and formatting relevant data from onboarding events.

Core Features & Use Cases

  • Automatic Data Extraction: Pulls data such as Lark display name, department, onboarding date, and user ID from onboarding events.
  • Connector-Ready Payload: Generates payloads that are ready to be used with the NyxID Lark approval connector.
  • Use Case: After Aevatar has processed an onboarding event from Lark, use this skill to create the necessary payload for a new employee's Lark approval instance without manual data entry.

Quick Start

To generate a Lark approval payload, run the skill with the onboarding event details.

Frequently Asked Questions about lark-onboarding-email-approval-payload-builder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate creating Lark approval payloads for new employee onboarding?

To automate Lark approval payload creation, you can use this skill to automatically extract user and department data from onboarding events and format it into a connector-ready payload without manual entry.

What data is required in a Lark onboarding event to generate an approval instance payload?

A Lark onboarding event must contain specific information about the user and department, including the Lark display name, department, onboarding date, and user ID, to successfully generate the approval payload.

Can I use the generated Lark approval payload directly with the NyxID Lark approval connector?

Yes, the generated Lark approval payload is connector-ready and can be used directly with the NyxID Lark approval connector to submit a new employee's approval instance.

When do I need to build a Lark onboarding approval payload after processing an onboarding event?

You need to build a Lark onboarding approval payload after Aevatar has processed an onboarding event from Lark, ensuring the necessary payload is created for the new employee's approval instance.

Does this skill require manual data entry for Lark display name and department details?

No, this skill does not require manual data entry because it automatically pulls data such as the Lark display name, department, onboarding date, and user ID directly from the input onboarding event.

What are the limitations of using automated data extraction for Lark approval payloads?

The automated extraction is limited to onboarding events that already contain the required specific user and department information, meaning incomplete input events will not produce a valid approval payload.