Fylamynt Product Docs
  • Welcome to Fylamynt
  • Getting started
    • Onboarding Checklist
    • 1. Setting up your first Cloud Service target account
    • 2. Getting to know workflows
    • 3. Creating your first workflow using AWS Cloud Services
    • 4. Setting up your first Integration
    • 5. Setting up your first resource
    • 6. Creating your first Incident Response workflow
    • 7. Incident Management - Automatic workflow execution
    • 8. Quickstart - Fylamynt sample workflows
  • Integrations
    • Amazon EventBridge
    • Ansible
    • AWS
    • AWS Health
    • Container
    • Datadog
    • Elasticsearch
    • Generic Webhook
    • GitHub
    • Google Kubernetes Engine (GKE)
    • Humio
    • Instana
    • Jenkins
    • Jira
    • New Relic
    • Opsgenie
    • PagerDuty
    • Pulumi
    • Prometheus
    • ServiceNow
    • Slack
    • Splunk
    • Splunk On-Call (VictorOps)
    • Spot by Netapp
    • Squadcast
    • Sumo Logic
    • Teleport
    • Terraform Cloud
    • Terraform CLI
    • Twilio
    • Zoom
  • AWS Services
    • EC2
    • Service Health
  • RESOURCES
    • API Keys
    • CloudFormation Templates
    • CloudWatch Targets
    • EKS Permissions
    • S3 Buckets
    • SSH Targets
  • FEATURED WORKFLOWS
    • Stop or Terminate underutilized AWS resources
    • Rightsizing EC2 instances
    • Incident Response Automation
    • Application Performance Monitoring
  • Announcement
    • What's new?
  • Support
    • Contact Fylamynt
Powered by GitBook
On this page
  • Why do you need Integrations?
  • To configure an Integration in Fylamynt:
  • What happens when you configure an Integration?

Was this helpful?

  1. Getting started

4. Setting up your first Integration

Previous3. Creating your first workflow using AWS Cloud ServicesNext5. Setting up your first resource

Last updated 3 years ago

Was this helpful?

Why do you need Integrations?

  • Integrations are the building blocks of workflows created in Fylamynt.

  • Each Fylamynt integration exposes a set of actions that can be used to create a workflow.

  • Only after configuring the API credentials and authorizing the integration are you able to leverage the specific integration actions.

To configure an Integration in Fylamynt:

  • Click on "Settings" available in the left panel of the product.

  • You should by default be in the Integration tab

  • Scroll down to see the list of available Integrations

  • Select an integration that you would like to configure

  • Fill out the parameters presented to you on the screen.

    • To get detailed instructions for each parameter, click on the Documentation link which will open a new tab to the integration's documentation page.

  • Once all the parameters have been filled out, click "Authorize" to enable the integration instance.

What happens when you configure an Integration?

If the integration is a compatible workflow trigger then it can be selected as a trigger type when a workflow is created.

Each Fylamynt integration also exposes a set of actions that can be used in a workflow. The actions available for each integration are listed on the configuration and documentation page.