inkreachhub/inkreach-teable-cli
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(skill): update formSubmitted trigger docs for multi-form support

Browse Source 
Reflect the formId(formId) -> formIds[] change across skill + CLI + docs:
- skill api-reference/trigger-types.md: formIds array config + legacy note
- skill guides (automation-guide.md, cli-reference.md): --form-ids <csv>
- inkreach-cli: add --form-ids option (csv parse), keep --form-id legacy
- docs/automation/triggers.md: P1 formSubmitted marked done
- docs/automation/README.md: formSubmitted config fields updated
This commit is contained in:
yeuimu
2026-08-12 03:59:12 +00:00
parent ef013690f3
commit 73998173a8
5 changed files with 67 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.agents/skills/inkreach-teable/api-reference/trigger-types.md
+8 -3
View File
@@ -122,14 +122,19 @@ inkreach-teable trigger set <wfId> --type recordCreatedOrUpdated --table-id tblX
## 5. formSubmitted — When a form is submitted
```bash
inkreach-teable trigger set <wfId> --type formSubmitted --table-id tblXXX --form-id viwXXX
inkreach-teable trigger set <wfId> --type formSubmitted --table-id tblXXX --form-ids 'viwXXX1,viwXXX2'
```
**Config:**
```json
{ "tableId": "tblXXX", "formId": "viwXXX" }
{ "tableId": "tblXXX", "formIds": ["viwXXX1", "viwXXX2"] }
```
- `formId` is the **form view's id** (a view of type `form`).
- `formIds` is an array of **form view ids** (views of type `form`). The trigger
fires when **any** of the listed forms is submitted.
- **Legacy compatibility:** the older single-string `formId` key is still
accepted (migrated to `[formId]` automatically), so existing workflows keep
working.
- An empty `formIds` array means the trigger never fires.
**Output:** `record.id`, `record.fields.*`, `user`, `tableId`, `formId`.