Create Connector Actions as Components

use this mode to convert a vendor's api specification into individual turbine components, one per endpoint you can then use these components in playbooks or reference them in the ingestion process at the top of the widget, under select what you would like to create , choose connector actions (the other option is ingestion ) use start from beginning to reset the process at any time step 1 api specification upload or paste an openapi spec to discover available endpoints in the api specification area, either paste your api/swagger specification (json or yaml) into the text area or use choose file to upload a file optionally check skip deprecated endpoints to exclude deprecated endpoints from the next step select parse openapi spec to read the specification and discover endpoints step 2 select endpoints select the api endpoints you want to turn into reusable components the widget lists available endpoints (after parsing in step 1) a badge shows how many are selected (for example, 0 selected ) select the checkbox next to each endpoint you want to create a component for you can select up to 25 endpoints; once this limit is reached, the remaining endpoint checkboxes are disabled select continue to proceed if you have not parsed the spec yet, the widget shows please parse the openapi spec first to see available endpoints step 3 authentication configuration set up the authentication required to access the vendor api under authentication type , choose one none , api key , bearer token , basic auth , or oauth 2 0 the widget can prefill the type from the specification; for none , no authentication is needed create a new http asset or select an existing asset and configure credentials as needed the widget names a new asset productname asset , where productname is from the specification select continue step 4 test endpoints test your credentials against a selected get endpoint to verify access from the endpoint dropdown, select an endpoint select test endpoint to run the request with your configured authentication select continue when done only get endpoints that you selected in step 2 appear in the dropdown if none were selected, the widget shows no get endpoints available please select get endpoints first step 5 generate components configure additional settings and generate the components under additional settings for component component prefix — prefix for generated component names (defaults to the product name from the specification) base url — base url for api calls (for example, https //api panoraysapp com) under hero ai visible to hero ai — when enabled, the generated components are available to hero ai requires confirmation to execute in chat — when enabled, hero ai must get confirmation before executing these components in chat select generate components turbine generates one component per selected endpoint components are named componentprefix endpointname (for example, crowdstrike falcon get alerts ) each component name in the widget is a hyperlink to the component