Local connector starter kits for file to URL actions
These starter kits give developers a reviewable first slice of native connector code without claiming any third-party marketplace or package release.
- Reviewed by
- GetFileURL technical team
- Updated
- Status
- local starter kits, not published connectors
- Upload
- POST /v1/files with bearer auth and multipart file bytes
- Output
- url, file_id, content_type, size, expires_at
What this page answers
No. They are local starter kits for review and adaptation. GetFileURL should not claim Zapier, Pipedream, Make, or marketplace availability until publishing and verification work is complete.
- Reviewed by
- GetFileURL technical team
- Last updated
Review the connector shape before release work exists.
The files are checked into the repository and served as plain static examples so developers can inspect, copy, and adapt them locally.
Starter kit index
Explains what is included, what is intentionally excluded, and how to review the assets safely.
Zapier action draft
A Zapier Platform CLI create-action starter that accepts one file input and returns GetFileURL response fields.
Pipedream action draft
A Pipedream Node.js action starter that accepts a file reference and exports the returned URL metadata.
Keep the wording honest until publishing happens.
The starter kits are useful implementation assets, but they are not evidence that GetFileURL is available inside Zapier, Pipedream, Make, or any marketplace.
No publishing commands
The files do not register, push, publish, invite users, or submit anything to a third-party platform.
No secrets
API keys belong in platform auth or secret fields. The templates use placeholders and secret props only.
No package claim
The TypeScript SDK and these connector kits remain local until release automation and verification exist.
Use the kit that matches the workflow builder.
n8n already has an importable HTTP workflow blueprint. These two starter kits cover the next developer-owned surfaces without adding a full package workspace.
n8n blueprint
Use the existing importable workflow JSON when the user can send binary data through an HTTP Request node.
Zapier
Start from the create action when a Zap needs to turn a file field into a direct URL.
Pipedream
Start from the action component when a workflow step has a file path, file URL, or generated file.
Common questions
Are these official marketplace connectors?
No. They are local starter kits for review and adaptation. GetFileURL should not claim Zapier, Pipedream, Make, or marketplace availability until publishing and verification work is complete.
Can developers use the files now?
Yes, as local draft assets. Review them with a test workspace, keep API keys in the platform secret store, and adapt them before any release process.
Why not create a full connector package now?
A full package would imply release structure, platform submission, and maintenance policy. The first safe slice is small local action code plus clear docs.