createHttpConnection

Mutation

Create a new HTTP connection in a workspace. Each connection becomes a tool named custom_http_{slug} that Buzz can use to make authenticated API requests. IMPORTANT: "name" is a human display name (e.g. "Eric's Gmail Connection" or "GitHub API"). It must be unique within the workspace. Buzz derives the tool id from a slug of this name. IMPORTANT: For snippet setup, create this only after researching MCP vs HTTP, recommending HTTP as the right path with setup/API key/auth docs links, and receiving user confirmation. IMPORTANT: Unless you set nativeProvider, you MUST call discover_oauth_metadata before calling this. If discovery returns success, set authType to 'oauth' and use the discovered oauthAuthorizationUrl, oauthTokenUrl, and oauthScopes. Only use authType 'headers' when discover_oauth_metadata fails. For Hive-managed apps, set nativeProvider instead of client id/secret/URLs. Sharing works the same as custom HTTP connections. For authType "headers", either pass a "headers" object with auth credentials as key-value pairs (e.g. {"Authorization": "Bearer sk-xxx"}), or omit headers and call request_secure_input immediately after creation. Headers are encrypted at rest. Do not ask the user to choose header names or paste JSON unless the service docs require multiple secret fields. Set sharingType to "everyone" for workspace-wide access, "custom" to share with specific users, or "me" (default) for personal use only. After creating, inform the user that the new tool (custom_http_{slug}) will be available in their next conversation. For an SFTP server that a Buzz snippet reads, skip OAuth discovery: set authType "sftp", origin sftp://host:port, sftpUsername and sftpHostKeyFingerprint, then call request_secure_input with the field "sftpPassword". An SFTP connection is never a custom_http_ tool; snippets read it with buzz.sftp.

Returns HttpConnection .