Troubleshooting Intermittent Errors with the Dropbox ‘New File’ Trigger in Pabbly Connect

Status: Closed · Asked by Support on May 29, 2026 · 0 views

Pabbly Support — Question · May 29, 2026

Issue

The Dropbox New File trigger occasionally fails on the first run with an error such as:

Error in call to API function 'sharing/create_shared_link': Invalid…

Re-executing the same workflow manually from Task History typically succeeds. The same problem can also surface as the trigger appearing to “stop firing” after the workflow has been idle for weeks.

Cause

Two underlying behaviours produce the same set of symptoms:

Polling timing. The original Dropbox trigger polled the folder on an interval. When a shareable-link request was made the moment a file appeared, Dropbox occasionally returned a transient Invalid response. The retry on re-execute almost always succeeded because the file had fully settled.
Webhook subscription expiry. If a workflow waits a long time between events, Dropbox automatically deregisters the dormant webhook subscription. The trigger then silently stops receiving events until the subscription is re-registered.

Recommended fix — switch to the Instant trigger

Pabbly Connect has shifted Dropbox from polling to an instant, webhook-based trigger. The updated triggers are available under the Dropbox integration page:

https://connect.pabbly.com/integrations/dropbox

How to switch

Open the affected workflow.
Delete the existing Dropbox → New File trigger step.
Search for Dropbox and select New File (Instant).
Reauthorise the Dropbox connection when prompted.
Save the workflow and turn it on.

The Instant trigger removes the periodic-poll delay that caused the first-run failures.

Frequently asked follow-up questions

The Instant trigger fires but the file name and other file details are missing.

The Instant trigger does emit file metadata. If a downstream step appears empty, the cause is almost always that the action step has not been re-mapped to the new trigger’s response keys. Re-map the file name, path and shareable-link fields to the new response payload and the data will flow again.

I am receiving duplicate triggers for the same file.

Two known causes:

Webhook retries from Dropbox. Dropbox occasionally redelivers the same event. Add a Filter step that compares the incoming file_id against the previously-processed ID (e.g. stored in a Google Sheet or Data Store) and skip when it matches.
Stale subscription. A workflow that has been waiting a long time may be running on an expired subscription. Open the trigger step, click Save without changing any configuration — this re-registers the subscription with Dropbox.

The trigger stopped firing entirely after several weeks.

This is the classic symptom of an expired webhook subscription. To resolve:

Open the workflow.
Click the Dropbox trigger step.
Click Save without changing the configuration.

Re-saving the trigger re-registers the webhook with Dropbox. For long-running workflows, re-saving the Dropbox trigger every 2–3 months is a good preventive habit until automatic re-subscription is rolled out.