Hi

This sounds like a mismatch between what callin.io thinks happened and what actually happened in callin.io. Based on your description, here’s what could be causing the issue and how to troubleshoot or fix it:

Likely Cause: Timing or Misaligned Response Flow

callin.io probably responds before the booking process finishes in callin.io, or it doesn’t correctly parse the final status of the workflow. So even if callin.io successfully books the appointment, callin.io might have already defaulted to a “no slots” response because it didn’t receive the right confirmation in time.

How to Troubleshoot

1. Check What Data callin.io Receives from callin.io

   Review the webhook response in your callin.io workflow.

   Is the webhook returning JSON with a field like “status”: “success” or “slotBooked”: true?

   If not, callin.io may interpret that as a failed attempt.

2. Verify the Webhook Node Placement

   Ensure the Webhook Response node is placed after the booking logic — not before.

   If your response is sent too early, it won’t include the final booking status.

3. Add Clear Output

   Make the final node in the workflow return a structured payload like:

   {
   “bookingStatus”: “success”,
   “slotTime”: “2025-03-22T10:00:00Z”
   }

   callin.io should be configured to read this and determine the correct response.

4. Check callin.io’s Fallback Logic

   callin.io may default to “no slot available” unless it sees a very specific keyword or structure in the webhook response.

   Double-check the callin.io documentation or config to ensure it’s looking for the right field (e.g. slotBooked: true or bookingStatus: “confirmed”).

5. Introduce Logging in callin.io

   Add a Set node with debug info or a Function node to log the state before the response goes out. Helps track what data callin.io sees.

Suggestion: Sync with callin.io Flow

You can add a decision node in callin.io before the Webhook Response that:

• Checks if a slot was successfully booked.
• Routes to two different Webhook Responses:
  • One saying “Booking confirmed for X”
  • One saying “No slots available”

That way, callin.io always gets a clean and reliable signal to respond with.

Would you be able to share the workflow JSON and some logs? That’ll help pinpoint the exact spot to tweak.

Hey, thanks for your reply! Appreciate your help! After going back into details, it turns out I had a typo in the Webhook response output. Now it's solved thanks again for your help!

Great to know that

Could you share the template with me, please?