Channels from the command line
Listing channels, groups, settings schemas and calling platform-specific tools.
integrations:list
The connected channels, with IDs. This is the starting point: every other command asks for that ID by this name.
posty integrations:list
# only the ID and the name
posty integrations:list | jq -r '.[] | "\(.id) \(.name)"'integrations:groups
The list of client groups. In agency use, this is how you manage one client's channels together. The Client groups page covers them.
posty integrations:groupsintegrations:settings
A channel's posting rules, its settings schema, the character limit unlocked for the account, and the tools you can call on it.
posty integrations:settings <channel-id>The schema applies to the connected account, not to the platform in general. This is the exact source for which fields are required, and which values they accept. The Platforms section has the per-platform overview.
integrations:trigger
A platform-specific lookup on a channel, such as the list of Discord and Slack channels or Pinterest boards. Google Business locations will work the same way once that platform arrives, it is coming soon. You need these because settings fields expect an ID, not a name.
# the schema lists the names of the tools you can call
posty integrations:settings <channel-id>
# then call the tool
posty integrations:trigger <channel-id> <tool-name>
# with parameters
posty integrations:trigger <channel-id> <tool-name> --data '{"key":"value"}'You cannot connect a channel from the command line: the platform asks a person for consent. See the Connecting a channel page.
The same thing from the API is the Call a channel tool endpoint. The contents of --data are the same JSON.