Add +form-public-link command to generate or read form share links
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 17.3k
- Forks
- 1.4k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 105
Description
Summary
Currently lark-cli can create forms (+form-create), configure questions (+form-questions-create), and submit form responses (+form-submit), but cannot generate or enable public share links for a form. Users must open the Base web UI to enable external/anonymous form access and copy the share URL.
Problem
When building agent workflows that involve form collection, the CLI cannot complete the full cycle — it stops at form creation and response submission, leaving the share-link step as a manual web UI operation.
Proposed Solution
Add a +form-public-link shortcut (or separate +form-share-create / +form-share-read commands) that wraps the underlying /open-apis/base/v1/forms/{form_id}/versions/{version_id}/sharing endpoint:
- Generate a new share token / public link for a form
- Read the current share link for a form (if already enabled)
- Optionally enable/disable public access
Use Case
An AI agent sets up a customer intake form via CLI, enables the public share link in the same session, and sends the link to the customer — all without touching the web UI.
Notes
This gap was noted by a collaborator in #1221: the Base Form + Workflow workflow is otherwise complete via CLI except for this share-link step.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the existing +form-create, +form-questions-create, and +form-submit commands, then inspect the /open-apis/base/v1/forms/{form_id}/versions/{version_id}/sharing endpoint described here. Define whether the command generates, reads, and optionally toggles a public link, and consider the work done when the full form workflow no longer requires the web UI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100