Track releases
When a release is published in Export SDK, add a row to Microsoft Excel.
See all Export SDK + Microsoft Excel integrations or talk to a human
Google for Startups AcceleratorHow Knit builds this workflow
The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.
Export SDK Explore Export SDK →
TriggersFires when a job, build or file conversion finishes in Export SDK.
Fires when a job, build or API request fails in Export SDK.
Calls an Export SDK endpoint with data from an earlier step.
Creates a PDF, image or converted file with Export SDK.
Checks or enriches a phone number, address or IP with Export SDK.
Microsoft Excel Explore Microsoft Excel →
TriggersFires when a row is added to a sheet in Microsoft Excel.
Fires when a row or column changes in Microsoft Excel.
Fires when a new spreadsheet or worksheet is created in Microsoft Excel.
Adds a new row to a sheet in Microsoft Excel.
Updates the values in an existing row in Microsoft Excel.
Finds a row by a column value in Microsoft Excel.
More Export SDK + Microsoft Excel workflows
See all Export SDK + Microsoft Excel integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Track releases” between Export SDK and Microsoft Excel?
Yes — describe it in the box above and Knit's Integrations Agent researches Export SDK and Microsoft Excel's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.
How long does it take to build?
Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.
Can issues be logged in a spreadsheet?
Yes. New or updated issues in Export SDK can be added as rows in Microsoft Excel for reporting.
Can a row create an issue?
When a row is added in Microsoft Excel, Export SDK can open an issue with its details.