Job Title: Fix Claude API Parameter Configuration in Bubble (1 hour)
Description:
I have a Bubble app for contract analysis with the following already built:
User authentication with company structure
Database (User, Company, Contract data types)
Dashboard page with contract input
Claude API integration that currently works BUT uses hardcoded sample contract text
The Problem: My Claude API call (in API Connector) has a hardcoded sample contract in the JSON prompt instead of accepting dynamic contract text. When users paste contracts, it always analyzes the same sample contract instead of their actual contract.
What I Need: Configure the existing Claude API call to:
Accept the contract text as a dynamic parameter
Pull from either the multiline input field OR the Contract database field (contract_text)
Test that it works with real contract input
Current Setup:
Index page has the Claude API call configured
JSON Body includes the full prompt but with hardcoded sample text at the end
Need to replace hardcoded text with dynamic parameter
Deliverable: Working AI contract analysis that processes actual user-submitted contracts instead of the sample text.
Budget: $75-150 for 1-2 hours of work
Timeline: ASAP - ideally completed within 24-48 hours
This clearly explains the problem and what you need fixed without requiring them to understand your entire project.
I’ve built and debugged dozens of OpenAI/Claude API integrations in Bubble, including multi-step prompts, dynamic field injections, and real-time input handling via database or frontend input. Your use case is straightforward and something I can wrap up quickly.
You’re likely just missing the dynamic binding in the JSON body inside the API Connector. I can jump in, replace the hardcoded sample with multiline input’s value or Current Contract’s contract_text, whichever you’re using, and ensure it works seamlessly on both the frontend and backend workflows. I’ll also test with a couple of contracts to confirm that it properly parses and responds.
This is a quick win, can finish within a couple of hours. Let me know if you’d like me to get started.
You should post screenshot of your settings in API connector and workflow as it seem to be really easy to fix and someone could help you for free directly here…
It could be a very easy fix. A one-hour coaching session should help. Otherwise, posting a screenshot could be a free way but might take a bit longer to fix. Hope to talk with you soon.
Problem Description
I have a Bubble app with a Claude API integration that currently uses hardcoded sample contract text instead of dynamic user input. The API call works but always analyzes the same fake contract regardless of what users enter. Current Setup Location: Index page, Workflow tab, “Button Analyze Contract is clicked” workflow, Step 1 - “Claude Analysis - Claude Analysis” What’s wrong: The Body (JSON object) contains a detailed administrative analysis prompt that ends with hardcoded sample text: "This is a consulting agreement between ABC Corp and XYZ Services for $5000 monthly with Net 30 payment terms." What needs to happen: Replace that hardcoded sample contract text with a dynamic parameter that pulls actual contract text from either:
Option A: Current Page Contract's contract_text (preferred - Contract is passed via URL from dashboard)
Option B: Multiline Input Paste Contract Here of Analysis's value (fallback for manual entry) Page Configuration
The index page is configured with:
Type of content: Contract
Data source: Get data from page URL
Contracts are created on the dashboard page and passed to index via “Go to page index” with “Result of step 1” (the Contract record). What You Need To Do
Edit the Claude Analysis API call Body (JSON object)
Remove the hardcoded sample contract text at the end of the “content” field
Configure it to accept dynamic contract text as a parameter
Map that parameter to Current Page Contract's contract_text
Test that it analyzes actual user-submitted contracts instead of the sample Expected Outcome
When a user enters a contract on the dashboard and clicks “Analyze Contract,” the AI should analyze their actual contract text, not the hardcoded sample.
Thoughts on this…can you address my issue?
You just need to make the contract part of the json object in api call dynamic by enclosing it with < contracttext >. This will expose a parameter contracttext in the api call in workflow and there you can set it as current page’s contract text or multline input’s value whichever is applicable .
This should be an easy fix. Just need to show some screenshots of your API connection so we can quickly diagnose it for you. The solution is probably what everyone has already said. We just need to show you how to fix it.