Branch logic with Calendly App Integration

Hi @talon256 Thanks for stopping by the community! Since the booking with Calendly is made outside of the form in their product, it isn’t possible to set a logic based on whether or not they have booked an appointment, I’m afraid. Typeform isn’t yet able to obtain that data while the form is being filled out. 

The best suggestion would be to use the workarounds suggested here: 

• Calendly is hurting my Typeform submission rates - simple fix?

Hopefully this helps a bit!

@Liz, thanks for the response. Hopefully the workaround you posted works for others! I’ve been active on that thread as well, unfortunately, the workaround isn’t a perfect fix (see my linked issue in the first line of the original post). I suppose that’s why it’s called a workaround!

I’m intrigued when you say that Typeform isn’t able to obtain Calendly data. It makes sense that Calendly wouldn’t return any of the user input data, but Typeform is already implementing the data needed to make ‘is unanswered’ logic work with the Calendly app.

What I’m referring to is the completion data. It’s that data point that allows the Calendly question to be a required* answer. (A working feature I’m very thankful for!) The same data point that tells the form to error on submission due to the question being left incomplete is the data point that can be used in the logic flow that would resolve my situation here.

If I’m assuming something incorrectly on the back-end function, let me know. 

Thanks!

Thanks, @talon256 ! Since the completion of the Calendly event would require that data to be sent back into the Typeform, this isn’t possible at this time. Of course, if there are any updates to the integration, we’ll post them here!

@Liz, can you explain how the ‘required question’ function is working correctly for the Calendly app if the data isn’t available to Typeform?

(I’d quote the response I received from Support when they first said it’s possible (which it is--and working well), but I haven’t been able to track down the email.)

Hi @talon256 I’m not sure I understand the question. Could you provide screenshots of what you’re looking to set up?

Thanks for asking, @Liz. Screenshots of the ideal setup are above in the original post. 

To clarify the question about the ‘required question’ function:

You originally said that 

As I’m re-reading, I wonder if your phrase "completion of the Calendly event” was actually referring to completing the event itself? When I’m referring to completion data, I’m talking about the binary data that Typeform tracks to determine whether each question has been completed or not.

In a private conversation with Typeform support, they explained to me that completion data for the Calendly app is maintained by Typeform (not Calendly). That’s how it’s possible to mark a Calendly app question as ‘required’ so that the form can’t be submitted without actually scheduling a meeting when the option is checked. (see screenshot below)

Since the function of the form as-is (with the ‘Required’ function successfully implementing via the question’s binary completion data), I wanted to delve into why that same binary data couldn’t also be used to provide a ‘is answered’ logic to branch to form, not just throw a ‘complete this question to submit’ error.

My apologies for the confusion. For me it’s more difficult to describe ideas like this via messaging than in conversation. Thanks for your help,

Hi @talon256 This isn’t a feature of the app yet, as it’s a relatively new app released. Of course, I’m happy to share this feedback, especially about the logic jump portion, to the product team. 

That would be great! From an outside view it seems like all the pieces are there, they just need to be connected. 

Of course, things are always more simple to ask for than it is for the devs to create...go product team! We believe in you!

Thanks, @Liz!

Thanks for your encouragement, @talon256! I'm sure our developers will appreciate it! Can't wait to get this up and running so you'll have a flawless integration with Calendly!