I am using multiple platforms to run a business. I provide 14 tutorial videos to my users after they create an account. What I want is when user sign up, my system should send 1 video / day to that user. Like this
video 1 on day 1
video 2 on day 2
...
...
video 14 on day 14
I want to make a setup in zapier to do that. Zapier should send each video a day unto 14 days a user gets registered.
Can anyone guide me how I can Achieve that target?
It's possible with Zapier, but will use a lot of steps + tasks. You could make a many-stepped zap that is structured like:
New User trigger
Delay until "tomorrow" (Zapier translates this into the correct date at runtime)
Send email w/ video 1
Delay until "2 days"
Send email w/ video 2
etc...
This will work, but probably be too expensive (that's a lot of Zapier tasks). Instead, look into drip email campaigns from any of the popular mail-sending services (such as Mailchimp).
Related
We are building a voice calling application ie (https://github.com/twilio/voice-quickstart-ios#11-make-client-to-client-call), calling working good with great sound quality. We have a new requirement to schedule a call outside of the application, ie instead of the call occurring through the application, it will occur by a normal dial-in number.
Our use case as follows
Caller clicks on agents profile.
The caller sees a list of available dates/times that agents are available. Let's say April 10th at 1 pm PST is available.
Caller selects April 10th at 1 pm and presses "Schedule".
The caller is prompted to pay $100 for a 1-hour call at the selected time.
The caller enters credit card information and presses "Pay".
The caller sees a confirmation message:
Your call is now booked with John Smith! Please call (555-555-5555 -
Twilio number) at 1 pm on April 10th, 2020.
We want to know the following
If a user calls to a Twilio number, can we redirect that call to our agents(ie we have several registered agents in our application)
When users calling, we want to know who is calling and where to redirect this call.
I think we can manage scheduling with our application logic. Let us know, what all services Twilio provides for executing such a scenario, we would love to know is there is any other way around. Your help is much appreciated.
Thank you.
You can look at products such as Twilio Studio. Studio allows you to easily set-up a call forwarding scenario, but the hyperlinked article has many way to accomplish this task. It sounds like you have already built out the agent assignment functionality.
I'm building a small event reminders app in Rails - you can see a list of live streams happening in the future, go to each event page, and add a phone # to be reminded about that event 5 minutes before it happens, with a link to the livestream itself.
What is the best way to model this? I was thinking 'Events' with the event details, 'Reminders' with an event_id and phone# attached. Also was thinking of using Active Job for the background processing.
you can use cron job to check about the event and reminder him before 5 minutes
and check about if event will remind more than one.
I'm building a group chat app in Swift 2. I want to set a 48 hour (or any other duration) timer for people to respond/contribute to the group conversation. If they don't they're out of the group chat. How do I do this?
I'm using the latest version of Xcode, and as mentioned above, I'm programming in Swift 2.
You can set background "timers" in your iOS app using UILocalNotification, but I've put timers in quotes because all it would do is show an alert on your user's screen after 48 hours have passed – it wouldn't actually boot them from the group chat.
The solution, then, is a server problem: however you are exchanging data between clients needs to be able to say, "sorry, you've been away too long" when the user tries to return.
The exception is if you're exchanging the messages using iCloud, then yes this would be app code: you'd need to query your public database to fetch the latest date the user contributed, and block them on the device from contributing further.
I have a quick question regarding the rate limits for Twitter Favourites - specifically the GET favorites/list call. I built favourites.io to keep track of my favourites. It lets you search and organise your favourites.
Anyway, it works as follows:
You sign up and authorize the application
It imports your favourites (every 15 minutes it makes a call to GET
favourites/list and imports any new tweets that you favourited)
It uses the user's access token to make the call
When checking the log file I noticed that one of the import jobs failed for a particular user. The error was: "Rate Limit Exceeded".
My understanding was that an authorized user could make 15 requests in a 15 minute window (and each request could return a maximum of 200 favourited tweets)
My job was running once every 15 minutes, so I'm not sure why that user is getting the "Rate Limited Exceeded" error.
Why might this be happening?
Thanks in advance,
Ross
It really comes down on how you built your script. If you're doing the timer from your side, it might not coincide with the one Twitter has.
For example if you send 1st call at 12:00:00 PM there's some latency lag (minor) by the time it gets to Twitter let's say 12:00:02. Now twitter expects the next call no sooner than 12:15:02, but if you have the timer script running every 15 minutes from your side, it'll send the second one at 12:15:00 < 12:15:02 so twitter rejects your call.
I would say start increasing the timer by 1-3 seconds (1 to be liberal, 3 conservative) until you give some room for Twitter to get and process your request.
I'm working on a mobile game with increasing daily bonuses based on the number of consecutive days they played (up to 7 days in a row before resetting). I'm looking to increase retention by using push notifications to remind players to log in for their Daily Bonus.
The support staff at our push notification service said this: "This is possible however we don't have any automatic tracking in place for this. It can be done with tags but you will need to add the logic in your app. You could do this by saving the last time the user used your app and then when they come back to your app compare the time. Each time they come back you can just increment your local consecutive days value and then set a tag to match."
If anyone could give advice on how to set this up that would be great. I appreciate the help.