Create Instance From Manifest
CONNECT-A-CAPABILITY FLOW step 1 (REST/Pipedream variant): define the integration here, then install it for the current identity with integration_install. Add a new REST 'connected tool' owned by the calling identity, built from a Pipedream component's source on github.com/PipedreamHQ/pipedream (pass component_path as the directory name under components/, e.g. 'perplexity' for components/perplexity/). Unlike integration_create_from_openapi, this parses hand-written JavaScript rather than a declarative spec, so it ONLY converts actions in one narrow, verified shape: a plain string _baseUrl(), a Bearer this.$auth.<field> auth template, and a flat (no conditional/computed) request body. Actions outside that shape are skipped, never guessed at - the response's skipped_actions lists every one with its reason, so tool_count can legitimately be less than the component's total action count, or even zero (a clear error, not a silent empty registration). connection_mode is required, no default: pass 'shared' or 'per_caller'. For a secured manifest (bearer or API-key auth) with no secret available yet, pass allow_unconnected=True to create the row unauthenticated -- the auth scheme is still recorded and the installer supplies their own credential at connect time.
Request
- Base URL: https://app.thinqos.com (the document declares no server; this is the origin it was published from)
- URL: https://app.thinqos.com/api/integrations/instances/from-manifest
- Auth: none declared
Headers
Request body
Response
Successful Response
Changes
No recorded changes to this operation across all 3 revisions of this API.