productivity
Gravity Forms CLI for Headless Automation
Use the Gravity Forms CLI for headless automation with headless JSON commands, schema discovery, credentials, and permission controls.
7 functions 6 read 1 write API key auth
Gravity Forms CLI for Headless Automation
Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers.
Use headless automation when another tool needs a stable local command surface. The Gravity Forms CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.
Command Shape
# Gravity Forms CLI for Headless Automation
kosmokrator integrations:configure gravity --set api_key="$GRAVITY_API_KEY" --enable --read allow --write ask --json
kosmo integrations:call gravity.gravity_list_forms '{"limit":1,"offset":1}' --json Discovery Before Execution
Agents and scripts can inspect Gravity Forms docs and schemas before choosing a function.
kosmo integrations:docs gravity --json
kosmo integrations:docs gravity.gravity_list_forms --json
kosmo integrations:schema gravity.gravity_list_forms --json
kosmo integrations:search "Gravity Forms" --json
kosmo integrations:list --json Useful Gravity Forms CLI Functions
| Function | Type | Parameters | Description |
|---|---|---|---|
gravity.gravity_list_forms | Read | limit, offset | List forms available in Gravity with optional pagination. |
gravity.gravity_get_form | Read | form_id | Get details for a specific Gravity form. |
gravity.gravity_submit_form | Write | form_id, data | Submit a Gravity form with field values. |
gravity.gravity_list_submissions | Read | form_id, limit, offset | List submissions for a specific Gravity form. |
gravity.gravity_list_entries | Read | form_id, limit, offset | List entries for a specific Gravity form. |
gravity.gravity_get_entry | Read | entry_id | Get details for a specific Gravity entry. |
gravity.gravity_get_current_user | Read | none | Get profile information for the authenticated Gravity user. |
Automation Notes
- Use
--jsonfor machine-readable output. - Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
- Configure read/write policy before unattended runs; use
--forceonly for trusted automation. - Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.