Keep sending when HubSpot AI credits run out
Three minutes, one fix. If a HubSpot workflow personalises copy with an AI step and the portal runs out of AI credits, that step returns nothing and the send quietly stops. Branching on the AI action’s own success or failure state means the personalised message goes out when credits exist and a static one goes out when they do not.
What you will be able to do
- Spot the failure: no AI credits means no output, which means no message
- Branch on an AI action’s final state rather than on its content
- Move the existing send onto the success branch without rebuilding it
- Add a static, non-AI iMessage on the failure branch from the same line
Chapters
Timestamps open YouTube at that moment. 6 sections across 2:45.
- 0:02
The problem
When the portal is out of AI credits, the custom-prompt step produces no text, so the message that depends on it never sends.
- 0:20
The starting workflow
Contact trigger, an AI data agent running a custom prompt, then a Send iMessage that references the prompt output.
- 1:07
Add the branch
Insert a branch after the AI node on one property or action output, and pick the action’s final state or failure state.
- 1:40
Move the existing send
Use "move all actions" so the current send lands on the succeeded branch instead of being rebuilt.
- 1:56
Reference the AI output
On the success branch the message still uses the custom prompt response, exactly as before.
- 2:07
The non-AI fallback
On the other branch, add a second Send iMessage with static copy on the same phone line.
