[Lark] - New Destination

[jackcbrown89]

Added destination for sending usage to https://uselark.ai

Testing

Include any additional information about the testing you have completed to
ensure your changes behave as expected. For a speedy review, please check
any of the tasks you completed below during your testing.

• Added unit tests for new functionality
• Tested end-to-end using the local server
• [If destination is already live] Tested for backward compatibility of destination. Note: New required fields are a breaking change.
• [Segmenters] Tested in the staging environment
• [Segmenters] [If applicable for this change] Tested for regression with Hadron.

Security Review

Please ensure sensitive data is properly protected in your integration.

• Reviewed all field definitions for sensitive data (API keys, tokens, passwords, client secrets) and confirmed they use type: 'password'

[joe-ayoub-segment]

Thanks for the PR @jackcbrown89 - I'll schedule for review once you convert from draft.

[joe-ayoub-segment]

LGTM @jackcbrown89 ,
Couple of questions before I deploy this.

1. Does Lark have any standard event names or standard event data items / properties? if so, it might be worth adding some default mappings for these properties.
2. Do you also want to collect user profile details (first_name, last_name, email etc)? If so, it might be worth implementing an Action to handle identify() calls.

Also could you please email me your email address as I'll need to invite you to the partner portal. my email is [email protected]

Best regads,
Joe

[jackcbrown89]

Thanks @joe-ayoub-segment . I just sent you an email.

1. Does Lark have any standard event names or standard event data items / properties? if so, it might be worth adding some default mappings for these properties.

No, the event data and event names are all user-defined.

2. Do you also want to collect user profile details (first_name, last_name, email etc)? If so, it might be worth implementing an Action to handle identify() calls.

Not at the moment, as we don't have any guaranteed ways of mapping standard profile details to a Lark subject. That's also a user-defined identifier so we would risk creating duplicates.

[joe-ayoub-segment]

Thanks Jack, Looks good then, I'll depoy this tomorrow. Best regards, Joe

…

On Fri, Jan 2, 2026 at 6:38 PM Jack Brown ***@***.***> wrote: *jackcbrown89* left a comment (segmentio/action-destinations#3479) <https://urldefense.com/v3/__https://github.com/segmentio/action-destinations/pull/3479*issuecomment-3706004188__;Iw!!NCc8flgU!bkLUALbvBFvQYHf7XiXPqpuLGpIF9lIXxu5dPZZk8xBjS0pt6sQpuPO8n0UGGq35eJ7xiMzscYqGqmS7To7TGVSNuQ$> Thanks @joe-ayoub-segment <https://urldefense.com/v3/__https://github.com/joe-ayoub-segment__;!!NCc8flgU!bkLUALbvBFvQYHf7XiXPqpuLGpIF9lIXxu5dPZZk8xBjS0pt6sQpuPO8n0UGGq35eJ7xiMzscYqGqmS7To5wlYmgnw$> . I just sent you an email. 1. Does Lark have any standard event names or standard event data items / properties? if so, it might be worth adding some default mappings for these properties. No, the event data and event names are all user-defined. 2. Do you also want to collect user profile details (first_name, last_name, email etc)? If so, it might be worth implementing an Action to handle identify() calls. Not at the moment, as we don't have any guaranteed ways of mapping standard profile details to a Lark subject. That's also a user-defined identifier so we would risk creating duplicates. — Reply to this email directly, view it on GitHub <https://urldefense.com/v3/__https://github.com/segmentio/action-destinations/pull/3479*issuecomment-3706004188__;Iw!!NCc8flgU!bkLUALbvBFvQYHf7XiXPqpuLGpIF9lIXxu5dPZZk8xBjS0pt6sQpuPO8n0UGGq35eJ7xiMzscYqGqmS7To7TGVSNuQ$>, or unsubscribe <https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AK2F3MFNBWMZECXAZJW5PID4E23LHAVCNFSM6AAAAACPECSG2GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMBWGAYDIMJYHA__;!!NCc8flgU!bkLUALbvBFvQYHf7XiXPqpuLGpIF9lIXxu5dPZZk8xBjS0pt6sQpuPO8n0UGGq35eJ7xiMzscYqGqmS7To4_AlUrsA$> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[joe-ayoub-segment]

PR deployed