productivity
IFTTT CLI for Shell Scripts
Use the IFTTT CLI for shell scripts with headless JSON commands, schema discovery, credentials, and permission controls.
7 functions 7 read 0 write Bearer token auth
IFTTT CLI for Shell Scripts
Call integration functions from shell scripts with stable JSON input and output.
Use shell scripts for small local automations that need one or more integration calls. The IFTTT CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.
Command Shape
# IFTTT CLI for Shell Scripts
kosmokrator integrations:configure ifttt --set access_token="$IFTTT_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call ifttt.ifttt_list_services '{"limit":1,"page":1}' --json Discovery Before Execution
Agents and scripts can inspect IFTTT docs and schemas before choosing a function.
kosmo integrations:docs ifttt --json
kosmo integrations:docs ifttt.ifttt_list_services --json
kosmo integrations:schema ifttt.ifttt_list_services --json
kosmo integrations:search "IFTTT" --json
kosmo integrations:list --json Useful IFTTT CLI Functions
| Function | Type | Parameters | Description |
|---|---|---|---|
ifttt.ifttt_list_services | Read | limit, page | List services in IFTTT with optional filters. |
ifttt.ifttt_get_service | Read | id | Get detailed information about an IFTTT service. |
ifttt.ifttt_list_applets | Read | limit, page | List applets in IFTTT with optional filters. |
ifttt.ifttt_get_applet | Read | id | Get detailed information about an IFTTT applet. |
ifttt.ifttt_list_connections | Read | limit, page | List connections in IFTTT with optional filters. |
ifttt.ifttt_get_connection | Read | id | Get detailed information about an IFTTT connection. |
ifttt.ifttt_get_current_user | Read | none | Get the currently authenticated IFTTT 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.