- Create Data Connector Request
You can create a data connector by providing the required parameters.
A description of what this data connector does.
The internal description of the data connector. If omitted, it is an empty string.
The HTTP method used when calling the external API.
The URL of the external API endpoint. Supports template variables like {{order_id}}.
Whether the connector is used directly by Fin (true) or only in workflows (false). Defaults to false.
The user types this connector is available for.
[ "leads", "visitors" ]
Whether the connector requires customer authentication before executing. Defaults to false.
Whether authentication is bypassed entirely (public endpoint). Defaults to false.
Whether authentication is enforced. On workspaces where this is supported, it takes precedence over customer_authentication and bypass_authentication when sent together, and setting it to false disables OTP.
Whether to validate that all required data inputs have values before executing.
A sample JSON response from the external API. Auto-generates response_fields and sets configuration_response_type to mock_response_type.
{ "order": { "id": 12345, "status": "shipped" } }
{ "name": "Get Order Status", "description": "Looks up order status from an external service", "internal_description": "string", "http_method": "get", "url": "https://api.example.com/orders/{{order_id}}/status", "body": "string", "direct_fin_usage": false, "audiences": [ "leads", "visitors" ], "headers": [ { … } ], "data_inputs": [ { … } ], "customer_authentication": false, "bypass_authentication": false, "enforce_auth": true, "validate_missing_attributes": false, "mock_response": { "order": { … } }, "token_ids": [ "1234", "5678" ] }