integration-advisor

Guide data integration setup with provider discovery, authentication checks, and field mapping.

4|1|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/lytics/agent-skills --skill integration-advisor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: integration-advisor
Source: https://github.com/lytics/agent-skills/tree/main/integration-advisor
Command: npx skills add https://github.com/lytics/agent-skills --skill integration-advisor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides users from "I want to connect X" to a fully configured, running data integration. It clarifies which workflow to use, how to map fields, and how to configure provider connections across exports, imports, and enrichment scenarios.

Core Features & Use Cases

  • Provider discovery and authorization checks to determine the appropriate authentication method for a given provider and setup
  • Workflow recommendations for exports, imports, and enrichment scenarios, with trade-offs explained
  • Automated field mapping guidance and validation across providers, data types, and target systems

Quick Start

Describe your integration goal and I will propose the best workflow and field mappings.

Frequently Asked Questions about integration-advisor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure data integration workflows for exports and imports?

To configure data integration workflows, you define the provider connection, verify authentication, and apply automated field mapping guidance to align data structures between the export source and import target.

What is the best way to map fields across different data providers?

The best way to map fields across data providers is using automated field mapping guidance, which validates data types and target systems to ensure accurate synchronization across exports, imports, and enrichment scenarios.

Do I need an API token to set up provider authentication for data integration?

Yes, an API token is required for data integration authentication. The system enforces a three-layer architecture and supports OAuth2, API Key, or credentials to authorize provider connections during setup.

How does provider discovery work for connecting new data sources?

Provider discovery identifies the target data source and runs authorization checks to determine the appropriate authentication method, generating in-UI setup guidance to achieve a fully configured connection.

Can I use OAuth2 for authentication checks when connecting external providers?

Yes, OAuth2 is supported for authentication checks. The integration setup validates provider connections using OAuth2, API Key, or credentials, ensuring authorized access across exports, imports, and enrichment workflows.

When should I use data enrichment workflows versus standard imports?

Use data enrichment workflows to augment existing records with external provider attributes, whereas standard imports transfer bulk data directly into a target system, with trade-offs explained for each approach.