Message connection callback protocol

Bind platform callbacks to a specified message connection. Saved connection, channel instance, credentials, and platform account must agree. The connection ID in the path is not independent authorization.

Path and configuration

GET https://api.moi.matrixorigin.cn/v5/ingress-callbacks/{provider}/{workspace_id}/{connection_id}
POST /ingress-callbacks/{provider}/{workspace_id}/{connection_id}

Use callback_path from message connection details to construct a full public URL in the same environment. Do not merely replace an ID in a credential callback URL. The handler has no regular product identity wrapper, but admission validates connection Provider, receive_mode=callback, enabled, desired_state, nonempty channel_instance_id, current active/inbound channel facts, and account identity.

Connection validation, provider Webhook registration, and actual platform delivery are distinct operations. A test response or successful challenge does not mean a message task completed. GET currently supports WeCom only; do not infer GET verification for GitHub or all other platforms.

Decoding and reception

After binding checks, CredentialRef and version are resolved from channel facts, then platform signatures/encryption and identity are decoded. Slack, Lark, Telegram, and WeCom have separate message branches; WeCom smart bots also have callback-stream handling. Credential callback rules are not an alias for arbitrary message connections.

Challenges return platform responses directly. Processable messages become ingress envelopes with the current connection configuration version, channel instance, account, receive mode, and response credential version, followed by replay checks and reception. Empty messages or nontarget events may be acknowledged without a new task.

Platform acknowledgment is not an agent terminal state or completed external reply. Check subsequent tasks and messages through the connection’s read protocol. Callback pulls also use frozen routing; a later query does not readmit every event.

Limits and environments

The handler uses a2 MiB MaxBytesReader; oversized input may return 413/code 2. Shared error adapters return numeric code/message/details, but signature, account, disabled connection, and dispatch failures have separate reasons. HTTP status alone does not prove business completion.

No messages were sent to external platforms, Webhooks registered, or actual callbacks initiated for this group.

Last updated on