Allow longer / configurable API Connector request timeout (beyond ~60s)

Idea
1

Hey Bubble team & community :waving_hand:

The current ~60-second API Connector timeout is too short for today’s workloads—especially AI calls that do heavier reasoning. Please let us configure a longer timeout (e.g., up to 180–300s) per call and/or per app.

Why?

  • Modern AI calls (e.g., GPT-5-style “thinking” / tool-use chains), transcription, indexing, and document processing often exceed 60s even with optimized prompts and streaming.

  • Some third-party services legitimately take longer (video jobs, large PDF parsing, data exports), and failing at 60s creates brittle UX and unnecessary retries.

Request

  • Make the timeout configurable (per call + app default), up to ~300s
2

From my point of view, 60 seconds is very long already. I think that some API services should add webhook (async) once job is completed.

However, You should add your idea to ideaboard Suggest a Feature on the Bubble Ideaboard | Bubble (check if there’s not already similar idea you can upvote)

2 Likes