thinkwise-software-factory-web-connections

Creates and configures Web Connections and OAuth servers in Thinkwise Software Factory models.

5|Updated Aug 25, 2026
One-click install
npx skills add https://github.com/rkortThinkwise/sf-mcp-skills-temp --skill thinkwise-software-factory-web-connections-rkortthinkwise
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: thinkwise-software-factory-web-connections
Source: https://github.com/rkortThinkwise/sf-mcp-skills-temp/tree/main/thinkwise-software-factory-web-connections
Command: npx skills add https://github.com/rkortThinkwise/sf-mcp-skills-temp --skill thinkwise-software-factory-web-connections-rkortthinkwise

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Integrating external HTTP/REST APIs into a Thinkwise Software Factory model is error-prone when done with one-off http_connector process actions that re-enter URLs, headers, and credentials on every call. This Skill guides the creation of reusable, modeled Web Connections with proper authentication, endpoint definitions, response parsing, and process flow wiring. ## Core Features & Use Cases - Web Connection Modeling: Build the full connection object graph (base URL, authentication type, endpoints, parameters, headers, form fields, output parameters) through the sf/manage_webconnections domain. - Authentication & OAuth Setup: Configure basic, bearer token, API key, managed identity, or OAuth authentication, including encrypted credential storage and per-environment overrides. - Response Parsing: Define output parameters using JSONPath, XPath, or regex so API responses are parsed in the model rather than downstream. - Use Case: You need your Thinkwise application to call the HubSpot API. Use this Skill to create a web connection with the correct base URL and auth, model a get_contacts endpoint with a JSONPath output parameter, and wire it into a process flow with input/output bindings. ## Quick Start Ask the AI to create a Thinkwise web connection for a specific external REST API, including its authentication method, endpoints, and response parsing, and wire it into a process flow.

Frequently Asked Questions about thinkwise-software-factory-web-connections

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a web connection in Thinkwise Software Factory?

Create a web_connection row with base_url and authentication_type in the sf/manage_webconnections domain, then add web_connection_endpoint rows for each API call, followed by parameters, headers, and output parameters. Finally wire it into a process flow with a web_connection-type process action.

What is the difference between web connection and http_connector in Thinkwise?

A web connection is a reusable modeled definition of an external API with one base URL, shared authentication, and built-in response parsing. The http_connector process action re-enters URL, headers, and auth on every call with no reuse or override mechanism, so web connections are preferred for any reused integration.

Can I configure an OAuth server through the Software Factory API?

Not fully. The oauth_server entity in sf/manage_webconnections exposes only its key fields, not the client id, secret, endpoints, or PKCE settings. OAuth server configuration currently requires the Software Factory's own UI, so verify field availability before promising an API-driven setup.

Why does my Thinkwise web connection return a non parsable body error?

This almost always means a body parameter's pre-processing mode does not match its value. JSON-body parameters are auto-escaped by default, so if the value is already-serialized JSON, set that parameter's pre-processing to none and keep the body template static.

How do I use different credentials per environment for a Thinkwise web connection?

Use runtime configuration overrides or per-application IAM overrides, which mirror the base connection's fields without changing the model. Note that setting use_deferred_credentials disables both override mechanisms, since authentication is then supplied by the process flow at run time.