create-sync-extraction-action

Create a class extending glyvio_core.SimpleSyncAction decorated with @glyvio_core.Action, implement the protected fetch method returning rows, and import the file from the environment entrypoint. The sync engine then invokes it as a task's query engine on the configured schedule.

Use a SimpleSyncAction when the source has no generic sync connector, such as a Firebird database reachable only from the customer's network or a custom webservice. A plain baseQuery works only against dataSources already registered with the sync engine.

The engine integrates rows by field name: each key in a returned row is written into the identically named field of the target glyvio_structure entity. Keys a row omits are left untouched, so row keys must be spelled exactly like the target structure's fields.

integration_code is a stable, unique external key each synced row must carry. The sync engine matches on it to decide whether an incoming row creates a new record or updates an existing one, so missing or duplicated values cause duplicates or wrong overwrites.

Default to <relation>_ic, whose value is the related record's own integration_code; the engine resolves the internal id itself. Use <relation>_id only when the task deliberately targets a known Glyvio-internal id, which is the uncommon exception.

No. A SystemTool exposes a routine to the Jeannie AI agent and requires a manifest permission entry, while a sync extraction action is called only by the sync engine's scheduler and self-registers via the @Action decorator with no manifest entry.