Contact Field & HTTP Request: Ensure HTTP Requests Use Latest Contact Field Values
Tuiyu Pang
Issue Description:
Currently, when an AI Agent updates a contact field (e.g., $contact.specific_start_time) and immediately triggers a HTTP request that references that same contact field in the request body, the HTTP request does not reflect the updated value. Instead, it sends the previous/stale value of the contact field.
Current Behavior:
- AI Agent executes: Update $contact.specific_start_time = "13:45"
- AI Agent executes: Trigger HTTP request with body containing "specific_start_time": "$contact.specific_start_time"
- HTTP request payload receives the old value (e.g., "12:00" or empty) instead of "13:45"
Expected Behavior:
The HTTP request should automatically wait for the contact field update to be fully persisted and then use the latest value of that contact field in the request payload.
Impact:
This synchronization issue prevents reliable sequential workflows where:
- A contact field must be updated first
- An HTTP request must immediately follow using that updated field value
- The external API/system depends on receiving the correct, up-to-date data
Requested Solution:
Implement a synchronization mechanism that ensures contact field updates are persisted before executing HTTP requests, or provide a way for users to explicitly wait/confirm that the contact field is updated before triggering the HTTP request. This would guarantee data consistency between the contact record and external API calls.