Integration Guides

Step-by-step guides for connected systems, now including the audit evidence generated when integrations are toggled or changed.

Evidence systems under study

New evidence, privacy, and agent-control features now implemented.

The latest backend work strengthens enterprise-grade governance: tamper-evident audit records, cryptographic key rotation, encrypted sensitive fields, GDPR rights workflows, resource mutation evidence, and an AI Agent Registry.

codeimplemented surfacereview basisenterprise relevancestudy lens
A01
Tamper-Evident Audit Chainaudit_events
Hash chain + HMAC signatures

Gives enterprise reviewers a verifiable sequence of actions instead of a loose activity log that can be rewritten after the fact.

integrity
A02
HMAC Key Rotationsigning_keys
Versioned signing keys

Lets the audit chain keep cryptographic continuity while keys evolve, which matters for long-lived regulated environments.

continuity
P01
Encrypted PII With Lookup Hashessensitive_fields
Fernet fields + companion hashes

Protects sensitive identity fields while preserving operational search and ownership lookup without exposing plaintext.

privacy
G01
GDPR Data-Subject Rightsprivacy_requests
Export + erasure router

Supports export and erasure workflows so privacy review is part of the platform architecture, not a manual afterthought.

rights workflow
R01
Resource Mutation Evidenceresource_mutations
Shared audit hooks across routers

Turns creates, updates, deletes, executions, toggles, acknowledgements, and remediations into reviewable tenant-scoped evidence.

change lineage
AG1
AI Agent Registryagent_registry
Agent registry API + UI

Creates a controlled inventory for autonomous agents so organizations can study ownership, access, lifecycle, and operational state.

ownership

Getting Started with Integrations

meghIQ integrates with popular automation platforms to discover and monitor your automations. Each integration requires specific permissions and setup steps. Follow the guides below for your specific platform.

Security Note: All integrations use OAuth 2.0 or secure API tokens. We never store your passwords and follow industry best practices for credential management.

🔗

Zapier

Connect your Zapier account to discover and monitor all your Zaps

Requirements

  • Zapier account with API access (available on all paid plans)
  • Admin or owner permissions on the Zapier account

Permissions Needed

Read access to Zaps, execution history, and account information

Estimated Time: 5-10 minutes

Setup Steps

  1. 1Navigate to Settings → Integrations in your meghIQ dashboard
  2. 2Click "Connect Zapier" button
  3. 3You'll be redirected to Zapier's OAuth page
  4. 4Log in with your Zapier credentials
  5. 5Authorize meghIQ to access your Zapier account
  6. 6Select which Zapier accounts to connect (if you have multiple)
  7. 7Wait for the initial discovery scan to complete
🐙

GitHub Actions

Connect your GitHub account to discover all GitHub Actions workflows

Requirements

  • GitHub account with repository access
  • Personal Access Token with repo and workflow read permissions, OR
  • OAuth App authorization

Permissions Needed

Read access to repositories, workflows, and workflow runs

Estimated Time: 10-15 minutes

Setup Steps

  1. 1Go to Settings → Integrations in meghIQ
  2. 2Click "Connect GitHub"
  3. 3Choose authentication method: Personal Access Token or OAuth App
  4. 4If using Personal Access Token: Generate one with repo and workflow read permissions
  5. 5If using OAuth: Authorize meghIQ GitHub App
  6. 6Select repositories to scan (or scan all accessible repositories)
  7. 7Wait for workflow discovery to complete
⚡

Microsoft Power Automate

Connect your Microsoft account to discover Power Automate flows

Requirements

  • Microsoft 365 or Azure AD account
  • Power Automate license
  • Admin or flow owner permissions

Permissions Needed

Power Automate read permissions, flow run history access

Estimated Time: 10-15 minutes

Setup Steps

  1. 1Navigate to Settings → Integrations
  2. 2Click "Connect Power Automate"
  3. 3Sign in with your Microsoft account (Azure AD)
  4. 4Grant Power Automate API permissions
  5. 5Select the Power Automate environment to connect
  6. 6Authorize meghIQ to read flows and run history
  7. 7Wait for flow discovery to complete
☁️

AWS Lambda

Connect your AWS account to discover Lambda functions and serverless automations

Requirements

  • AWS account with Lambda functions
  • IAM permissions: Lambda read, CloudWatch read, API Gateway read
  • Access to regions where your Lambda functions are deployed

Permissions Needed

Lambda read, CloudWatch read, API Gateway read, EventBridge read

Estimated Time: 15-20 minutes

Setup Steps

  1. 1Go to Settings → Integrations
  2. 2Click "Connect AWS"
  3. 3Choose connection method: IAM Role (recommended) or Access Keys
  4. 4If using IAM Role: Follow the CloudFormation template setup
  5. 5If using Access Keys: Enter your AWS Access Key ID and Secret Access Key
  6. 6Select AWS regions to scan (or scan all regions)
  7. 7Configure CloudWatch access for metrics
  8. 8Wait for Lambda function discovery to complete
🔷

Azure Functions

Connect your Azure account to discover Azure Functions

Requirements

  • Azure account with Function Apps
  • Azure subscription access
  • Function App read permissions

Permissions Needed

Azure Functions read, Application Insights read

Estimated Time: 10-15 minutes

Setup Steps

  1. 1Navigate to Settings → Integrations
  2. 2Click "Connect Azure Functions"
  3. 3Sign in with your Azure account
  4. 4Select Azure subscription and resource groups
  5. 5Grant Azure Functions API permissions
  6. 6Authorize meghIQ to read function apps and execution history
  7. 7Wait for function discovery to complete
🤖

Jenkins

Connect your Jenkins instance to discover jobs and pipelines

Requirements

  • Jenkins server URL (accessible from meghIQ servers)
  • Jenkins user account with read permissions
  • Jenkins API token or username/password

Permissions Needed

Jenkins job read, build history read, pipeline read

Estimated Time: 10-15 minutes

Setup Steps

  1. 1Go to Settings → Integrations
  2. 2Click "Connect Jenkins"
  3. 3Enter your Jenkins server URL
  4. 4Choose authentication: API Token (recommended) or Username/Password
  5. 5If using API Token: Generate one from Jenkins user settings
  6. 6Enter Jenkins username and API token
  7. 7Test the connection
  8. 8Wait for job and pipeline discovery to complete

Troubleshooting Common Issues

Connection Fails

  • Verify your credentials are correct
  • Check that you have the required permissions
  • Ensure your firewall allows connections to meghIQ servers
  • Try disconnecting and reconnecting the integration

No Automations Discovered

  • Wait for the initial scan to complete (can take 10-30 minutes)
  • Verify you have automations in the connected account
  • Check that the integration has read permissions
  • Review the integration logs in Settings → Integrations

Permissions Errors

  • Review the required permissions for your platform
  • Update OAuth scopes or API token permissions
  • Contact your platform administrator if needed
  • Re-authenticate the integration with updated permissions
View Full Troubleshooting Guide

Next Steps

Once you've connected your platforms, explore these resources:

Getting Started Guide

Learn how to use meghIQ after connecting platforms

User Manual

Comprehensive guide to all features and capabilities