Recued
Menu
← Back to recipes

Fivetran Retrieve Connection Sync History

by recued-core v1 8 views

Non-chat, uncached, read-only Fivetran workflow over Retrieve Connection Sync History. It performs no configuration mutation, preserves the fixed api.fivetran.com origin boundary, and reports its completeness explicitly.

How it works 2 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (2 steps)
rows ?
scope to_summary
Format results as a summary card
Settings 2 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

fivetran setting =
connection id setting =

Trust & control

What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.

Permissions it requires

Read your Fivetran connection
Declared by the recipe — Recued grants these at install, where you review them before approving.

About

Tags

fivetran fivetrandata-integrationread-onlypack:fivetran-connections-data-pipeline

Details

2 steps 2 configurable settings recipe_id: connection-sync-history-fivetran