Create a table fed by an integration
Create the table, its imported-record column and a few extracted columns, then start loading rows in the background.
The table exists as soon as this returns, so the client can navigate to it immediately and watch rows arrive. Poll the run to follow progress.
Every record lands whole in one Object column. The extracted columns are formulas reading paths out of it, so a refresh updates them for free — and any field the import brought back can be given its own column later without re-fetching anything.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
What to import, and into a table called what.
The connected integration to import from.
Which object to import.
1 - 255Name for the new table.
1 - 255Which id key to match rows on; null elects one from the sample.
255Fields to give their own column, in this order. Null uses the preview's suggestions; an empty list promotes nothing. Unknown paths are skipped; the table's column limit is the only ceiling.
Most rows one run may pull; null for everything. A limited source can never sweep deletions — it cannot tell a record it chose not to fetch from one that is gone.
x > 0Response
Successful Response