The Intuned.json file is the configuration file for your Intuned project. It defines various settings including workspace information, replication settings, auth sessions, API access, deployment options, runtime defaults, and IDE metadata. This file should be placed in the root directory of your project.When you try to modify Intuned.json in the IDE, we will provide you with a UI that helps you modify the underlying JSON structure and describe what each property does. You can also switch to text mode to manually modify the JSON as you see fit. On the other hand, if you are working with locally using Intuned CLI to run and deploy your project, you will need to manually edit this file and ensure the JSON structure is valid.The main difference between the CLI configuration and the IDE configuration is that the CLI configuration requires additional properties that are used when you want to deploy your project like workspaceId and projectName but these configuration properties are not needed when working in the IDE.
The maximum number of concurrent executions allowed via Intuned API. This does not affect jobs. A number of machines equal to this will be allocated to handle API requests. Not applicable if API access is disabled.Default:1
Recorder finish URL for the recorder. Once this URL is reached, the recorder stops and saves the auth session. Required if type is "MANUAL". Not used if type is "API".
Whether to enable consumption through Intuned API. If this is false, the project can only be consumed through jobs. This is required for projects that use auth sessions.Default:true
Whether to run the deployed API in a headful browser.
Running in headful can help with some anti-bot detections. However, keep in mind that running in headful mode might increase resource usage , so keep in mind to choose appropriate machine size for you.
Default sink configuration by environment.Each environment accepts the same sink object used by run inputs.See Webhook Sink and AWS S3 Sink for the supported fields.
Sink configuration for deployed runs. See sink fields below.
Each sink object supports type ("webhook" or "s3"), skipOnFail (boolean, required), and apisToSend (array of API names, optional).Webhook sink additionally requires url and optionally accepts headers.S3 sink additionally requires bucket, accessKeyId, secretAccessKey, and optionally accepts region, prefix, endpoint, forcePathStyle.
The maximum number of concurrent executions allowed via Intuned API. This does not affect jobs. A number of machines equal to this will be allocated to handle API requests. Not applicable if API access is disabled.Default:1
Recorder finish URL for the recorder. Once this URL is reached, the recorder stops and saves the auth session. Required if type is "MANUAL". Not used if type is "API".
Whether to enable consumption through Intuned API. If this is false, the project can only be consumed through jobs. This is required for projects that use auth sessions.Default:true
Whether to run the deployed API in a headful browser.
Running in headful can help with some anti-bot detections. However, keep in mind that running in headful mode might increase resource usage , so keep in mind to choose appropriate machine size for you.
Default sink configuration by environment.Each environment accepts the same sink object used by run inputs.See Webhook Sink and AWS S3 Sink for the supported fields.
CAPTCHA solving settings that control automatic CAPTCHA detection and solving.
CAPTCHA solving requires headful mode to be enabled.
it’s recommended to also have stealth mode enabled and a proxy attached to the run for the best results.
This feature only works on the Intuned Platform and is not available during
local CLI development.
The CAPTCHA solving extension works better with newer Playwright versions. Upgrade to the latest supported version for improved solve rates. See Playwright and browser support.
CSS selectors for locating the CAPTCHA image element. Multiple selectors can be provided as fallbacks.Example:["#captcha-image", ".custom-captcha img"]
CSS selectors for the input field where the CAPTCHA answer is entered. Multiple selectors can be provided as fallbacks.Example:["#captcha-input", ".captcha-field input"]
CSS selectors for the button that submits the CAPTCHA answer. Multiple selectors can be provided as fallbacks.Example:["#submit-button", "button[type='submit']"]
CSS selectors for the input field where the answer is entered. Multiple selectors can be provided as fallbacks.Example:["#answer-input", ".captcha-answer"]
Delay in milliseconds before solving the CAPTCHA after it is detected. Useful for mimicking human behavior and avoiding bot detection.Default:2000 (2 seconds)