fivetran-custom-connector

Automate Fivetran custom SDK connector development with standardized schema, configuration, and testing.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Grupo-AFAL/claude-plugins --skill fivetran-custom-connector
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fivetran-custom-connector
Source: https://github.com/Grupo-AFAL/claude-plugins/tree/main/data-tools/skills/fivetran-custom-connector
Command: npx skills add https://github.com/Grupo-AFAL/claude-plugins --skill fivetran-custom-connector

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reduces the boilerplate and complexity of building AFAL Fivetran custom SDK connectors by standardizing how entities are defined, synced, and tested across GEOTAB, WMS, and FOCALTEC.

Core Features & Use Cases

  • Standard two-file connector architecture (connector.py and afalConfiguration.py) supporting the three Fivetran connector flavors.
  • Supports incremental and offset-based sync strategies with schema definitions in afalConfiguration.py and tests using the load_connector fixture pattern.
  • Provides testing scaffolding with mocked external SDKs to enable reliable unit tests and end-to-end validation for new entities.

Quick Start

Configure afalConfiguration.py with a new entity, implement schema() and update() in the connector, and run the Fivetran debug flow or unit tests to verify.

Frequently Asked Questions about fivetran-custom-connector

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

FAQPage Schema
How do I build a Fivetran custom SDK connector for incremental syncs?

To build a Fivetran custom SDK connector, you implement a schema() function and an update() generator in connector.py, then define your entity schemas and incremental sync parameters in afalConfiguration.py.

What is the load_connector fixture pattern for testing Fivetran connectors?

The load_connector fixture pattern is a testing scaffolding method that uses mocked external SDKs to enable reliable unit tests and end-to-end validation for new entities in Fivetran custom connectors.

Does this Fivetran connector architecture support offset-based pagination?

Yes, the connector architecture supports both incremental and offset-based sync strategies, standardizing schema definitions and data retrieval across GEOTAB, WMS, and FOCALTEC platforms.

What's the best way to standardize entity definitions across multiple Fivetran connectors?

Standardizing entity definitions is best achieved by using a two-file architecture with afalConfiguration.py for schema configuration and connector.py for implementation, reducing boilerplate across different connector flavors.

Do I need a specific schema() function to use the Fivetran custom SDK?

Yes, a schema() function is a strict requirement for the Fivetran custom SDK architecture, working alongside an update() generator to define data structures and execute data synchronization.

Why does my Fivetran custom connector require afalConfiguration.py?

Your Fivetran custom connector requires afalConfiguration.py to standardize how entities are defined and synced, separating schema configuration from the connector logic to simplify maintenance across GEOTAB, WMS, and FOCALTEC.