Integrations

Integrations with third-party applications and services are key to your success when using furl. There are three components to an integration:

Connections: the api key, password, or other details necessary to connect to the third-party API
Datasources: the capabilities used for furl to pull specific, useful data from the third-party tool into the furl knowledge graph
Actions: the capabilities allowed for users to perform an action in a third-party tool such as creating tickets or sending messages

Datasources

Atlassian Jira
- Issues → Import issues to track and identify past work that can improve your confidence.
Automox
- Devices → Import devices and policy relationships in order to better understand how remediations and patching is performed in your environment
- Policies → Import policies to understand the schedule, configuration, and scope of patch and remediation policies for your environment
AWS
- EC2 Instances → Import EC2 instances to gain knowledge of whether devices are hosted in AWS
Freshservice
- Tickets → Import tickets to track and identify past work that can improve your confidence.
Rapid7 InsightVM
- Assets [REQUIRED] → Import asset and vulnerability findings used by furl to group and prioritize projects and begin remediating security risks
- Vulnerability Definitions → Import vulnerability definitions to allow furl to have greater enrichment of the vulnerabilities in your environment

Freshservice
- Create Change Request → Plan and communicate work to your change board
- Create Ticket → Track and prioritize work across teams
Jira
- Create Issue → Track and prioritize work across teams
Slack
- Send Message → Coordinate work that needs performed with others