# Callback

Send notifications to GitHub or Slack

* [`sfp server callback post`](#sfp-server-callback-post)

## `sfp server callback post`

Post a callback notification to configured providers (GitHub, Slack, etc.).

```
USAGE
  $ sfp server callback post -e started|completed|failed|approval_requested|approved|rejected -p <value> -x <value>
    [--json] [--repository <value>] [-e <value>] [-t <value>] [--sfp-server-url <value>] [--loglevel
    trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL] [--close]

FLAGS
  -e, --email=<value>              Email address for authenticated user. Ignored if --application-token is provided. Can
                                   be set via SFP_SERVER_USER env var.
  -e, --event=<option>             (required) The event type: started, completed, or failed
                                   <options: started|completed|failed|approval_requested|approved|rejected>
  -p, --provider=<value>           (required) JSON configuration for the callback provider
  -t, --application-token=<value>  Application token for CI/CD authentication. Can be set via SFP_SERVER_TOKEN env var
                                   (CLI flags take precedence over env vars).
  -x, --context=<value>            (required) JSON context data for the callback message
      --close                      Close the callback target (e.g., close GitHub issue) after posting
      --loglevel=<option>          [default: info] logging level for this command invocation
                                   <options: trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL>
      --repository=<value>         The repository identifier. E.g `owner/repo` for GitHub/GitLab or `org/project/repo`
                                   for Azure DevOps
      --sfp-server-url=<value>     URL of the SFP server. Can be set via SFP_SERVER_URL env var or config: sfp
                                   config:set server-url

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Post a callback notification to configured providers (GitHub, Slack, etc.).

  This command is typically called from automated workflows to notify users of task status changes.

EXAMPLES
  `sfp server callback post --event started --provider '{"type":"github","github":{"repo":"owner/repo","issue":123}}' --context '{"username":"user@example.com","accessLevel":"admin"}'`

  `sfp server callback post --event completed --provider '{"type":"github","github":{"repo":"owner/repo","issue":123}}' --context '{"username":"user@example.com"}' --close`
```

*See code:* [*src/commands/server/callback/post.ts*](https://source.flxbl.io/flxbl/sfp-pro)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.flxbl.io/flxbl/sfp/cli-reference-v51-release-v3/server/callback.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.