*Only available for selected customers at this time*
Using integrations, you can easily integrate Detectify into your workflow and be alerted every time there are any Detectify updates - such as new critical findings on a flagship domain, started and finished scans, etc.
Detectify integrations are powered by Workato, a third-party tool that allows you to export results in the way that best suits you and your team.
Because Detectify relies on Workato’s fully embedded solution, Because Detectify relies on Workato’s fully embedded solution, you will learn different concepts that are unique to Workato’s environment.
Start using Integrations 2.0
Once you have read and accepted Workato’s Embedded Software Supplemental Terms, you will see a list with available recipe templates that Detectify’s team has set up beforehand.
You can use said recipe templates by following these steps:
Click on the View recipe button, found to the right of the template’s name and description.
In the next screen click on Use this recipe. This will trigger a popup modal within the Workato’s iframe.
In the popup modal, you will be asked to copy the recipe and save it in the selected project. Click on Copy and save to accept.
If your recipe requires customization, a new popup modal will appear, guiding you to the next step, where the recipe details can be modified. Click on Customize recipe to move forward.
Modify your recipe and solve any highlighted issues (for example, you might need to fix your Slack connection or choose the right Slack channel) and when you feel ready, click Save then Exit.
Clicking on Start recipe is the final step. You can always come back and stop, edit or remove the recipe.
Repeat the process to create more recipes and reach out to us at email@example.com.
Because Detectify relies on Workato’s fully embedded solution, you will learn different concepts that are unique to Workato’s environment. Below you can read what these different concepts refer to:
Recipes: A recipe is an automated workflow that connects your apps. Each recipe consists of a trigger and one or more actions. When recipes are started, they will run automatically in the background to look for trigger events and carry out recipe actions. When they are stopped, they will cease to look for trigger events. However, when a recipe is started again, it will pick up all the trigger events that occurred since the recipe was stopped. In other words, stop functions like pause.
Triggers: Triggers determine what event to listen to execute the actions described in a recipe. Trigger events can be set off in apps when a certain event happens.
Steps and Actions: Recipe steps are executed every time the trigger event occurs. Recipes are required to have at least one step.
Connections: For a recipe to communicate with apps via actions and triggers, it has to be authorized to interact with apps. This authorization is referred to as a connection. Connections are not tied to a recipe - a single connection can be used by multiple recipes.
Jobs: Each time there is a trigger event, the actions in the recipe are executed. The entire flow of each trigger event through the recipe is called a job. Jobs can be successful (when actions are executed successfully), or have errors (when an action results in an error). When an error is encountered, subsequent actions are not executed.
Assets: Workato refers to assets when referring to the existing folders, recipes, and connections available in an account.
You can learn more about Workato’s ways in their Getting Started Manual.