Slack

How it works

When someone mentions @goatfied in a connected Slack workspace, Goatfied launches a cloud agent with the message as its prompt. Because Slack doesn’t carry repo context, include a repo:owner/name tag so the agent knows where to work:

@goatfied repo:acme/web add a loading state to the checkout button

The agent clones that repo, makes the change on a fresh branch, and opens a PR. Follow its progress in the Agents Window or with goatfied cloud ls.

Set it up

An org admin configures this once:

1. Create a Slack app and subscribe to message events (app_mention).
2. Point the event request URL at https://api.goatfied.com/v1/triggers/slack.
3. Send us the app’s Signing Secret so we can enable it for your org. Every request is verified against the X-Slack-Signature header, with a timestamp replay guard, before any work begins.

Permissions

The agent only touches the repo named in the repo: tag, and every run is metered like other usage.