Request File Upload
pushbullet.upload_request
ActionChat & messagingconnection required
Calls the Pushbullet API with the connection's credentials.
Reserve an upload slot for a file and return the URL its bytes must be posted to before it can be pushed.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Pushbullet
- Secret shape
- the access token, or {"access_token": "…"}
- Config it needs
- device_iden
- Resolved by
- config.connection_id, else node.connection_id
Configuration
2 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
file_name Name to give the uploaded file. | string | Yes | — | — | cat.jpg |
file_type MIME type of the file being uploaded. | string | Yes | — | — | image/jpeg |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"file_name": "cat.jpg",
"file_type": "image/jpeg"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
file_name The name Pushbullet will store the file under. | string | — |
file_type The MIME type Pushbullet will store the file as. | string | — |
file_url Download URL to hand pushbullet.push_file once the bytes are uploaded. | string | — |
upload_url URL the file's bytes must be POSTed to as multipart/form-data. | string | — |
{
"file_name": "",
"file_type": "",
"file_url": "",
"upload_url": ""
}Related Pushbullet nodes
See Request File Upload run in a workflow.
In a technical demo we add the Pushbullet connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.