Hi, there’s two scenarios I’d like to solve via Pipedream.
What I need
Scenario 1) Someone books an event on Cal.com - this is the trigger. The next step is to check if this contact already exists in my email list on AWeber. Based on this info, there shall now be a split in paths (which I need help with):
- path ‘contact exists in AWeber’: update existing contact with a tag ‘new booking’
- path ‘contact does NOT exist in AWeber’: create new contact with name and email from Cal booking and add same tag ‘new booking’
Scenario 2) After the end of each Cal.com booking, a workflow shall be triggered that updates the contact in AWeber with a tag ‘booking completed’.
What I’ve tried / have issues with
a) I can’t figure out how to create that ‘split path’ in scenario 1. If I test either of those, i.e. creating a new contact or updating an existing one, things work just fine. But I can’t figure out how to combine those into one workflow that first ‘checks list’ and then either ‘creates contact’ or ‘updates contact’.
b) The workflow I created to update a contact with a tag after the Cal event ended, does work - but ONLY if I test/trigger it manually. Which defeats the whole purpose… I’ve tested multiple events with different event durations, but somehow it seems that after the end of any Cal event there’s never an automatic trigger of ‘event ended’. It just never runs automatically and I don’t know why.
Any help is very much appreciated! Thanks!
Hello @meisatei,
First off, welcome to Pipedream! Happy to have you!
Unfortunately, Pipedream have not yet offer branching capability for now, Pipedream has a ticket here to track it.
May I ask what specific actions on Aweber you’re using? Are they Add Subscriber and Update Subscriber?
Hi @vunguyenhung,
Thanks for your reply! I see, hopefully we’ll be able to split workflows into branches soon.
Exactly, I’m using AWeber ‘Add Subscriber’ and ‘Update Subscriber’.
For the trigger side coming from Cal, it’s ‘New Booking Created’. For scenario 2, it’s ‘Booking Ended’, which doesn’t seem to work as mentioned in initial post.
Hello @meisatei,
I think this is better be done on Pipedream side. I’ve created an issue here to help you for your usecase. Kindly subscribe to the ticket to be noticed when it is done, after that you should be able to use the new action to create or update AWebe subscriber
1 Like
Hi @vunguyenhung,
I finally get to test this after it has been completed in #5937.
But I still need to clarify again to set it up correctly… There are still the two cases and the different actions that have to be completed for each of them. So…
1) NEW subscriber (books Cal meeting, and does NOT exist in AWeber yet)
- action: create new subscriber in AWeber by using email AND name from Cal booking
- action: add tag “new booking”
2) EXISTING subscriber (books Cal meeting, and DOES already exist in AWeber)
- action: search for existing subscriber by email only from Cal booking
- action: add tag “new booking”
This is how the setup should look like, is this correct?
And the most important question, do I need to add both of the sample expressions under “Tags”? I’m confused because they’re different for new and existing subscribers…
Thanks for your help.
@meisatei,
The structure for the tag is different becaus of AWeber API is not consistent. This is not in Pipedream control. Regarding your usecase, if the implemented action can not serve your need, would you mind submitting another ticket here for us to improve? Stating the action specification in more detail
Well, I’m not sure if the action works for me because I don’t know how to set it up in the first place. That’s what my question was. I’m new to Pipedream, so, sorry if this is just a newbie question…
I don’t know how to add those expressions shown as examples. How would I have to enter them? And do I need both at the same time?
That’s what the initial post from me was all about - I already explained the desired flow in every detail. There are only two paths this workflow needs to fulfil. Thanks.
Hi @meisatei,
I strongly recommend you to watch through this Pipedream university series to be more efficient with Pipedream.
Regarding your usecase, I think you can ignore the Tag prop in the Create or Update contac action, which will create or update a contact for you. Then after you have a contact created, you can use AWebe Update contact action to add the tag you want
For dedicated support for your usecase:
- If you have subscribed to Pipedream team plan, you will be added to a dedicated slack support channel
- If you’d like to hire a Pipedream expert for your usecase, feel free to use this link: Connect with a Pipedream Partner
