Set up your connector
Choose connector capabilities
Decide what your connector supports and identify the workers, mappings and permissions each capability needs.
Implement the capabilities your integration needs. Declare and test every capability you expose.
| Capability | Required implementation | Dependencies and verification |
|---|---|---|
| Sync-unit discovery | External sync units worker | Return stable units the connected account can access |
| Metadata | Metadata worker | Supply EDM matching extraction, including supported references and custom fields |
| Initial/incremental extraction | Data worker | Mapping, stable IDs, pagination, continuation and resolved time windows |
| Selective extraction | Scope filtering | Emit only enabled record types, including correct dependent references |
| Historical extraction | Time-window filtering | Honor resolved lower and upper bounds; verify provider filtering behavior |
| Attachment extraction | Attachment worker | Discover attachment metadata, resolve owners and stream authorized file content |
| Custom attachment processing | Processors | Stream files and preserve valid attachment/output associations |
| Permission import | Permission metadata and records | Principals, memberships and access rules; test restricted access |
| Team import | Team schema and membership mappings | Stable team/member identity and valid relationships |
| Reverse data sync | Data loader | External write scopes, supported operations, denormalization and identity mappers |
| Reverse attachment sync | Attachment loader | Owner mapping, accessible file stream and provider upload endpoint |
| Rich text/articles | Rich-text mapping | Target-specific format and attachment links |
The template and Asana may not implement every AirSync capability. Check each example's declared coverage in the code map.
Check the external API
Record the endpoints and scopes behind every claimed operation, a sample external response for each record type, supported field mappings, unavailable provider features and expected pagination/rate-limit behavior. Validate these against a provider test account before broadening the connector's manifest capabilities.
Last updated on