I am new at Zapier and trying to make an email verification using NeverBounce from Zapier and complete the following setup.
I create an app in NeverBounce.
I complete Trigger in steps in Zapier.
Completed the Action and logged in NeverBounce by IP key.
And finally, during testing, I get this error!
The verification could not be sent to NeverBounce.
The app returned `{"message":"We were unable to complete your request. Check our system status at https://twitter.com/neverbounceapi as their may be an issue with our system. The following information was supplied: Insufficient credit balance.
Here is an screen shoot of the error I am facing
Thanks for your help😊.
The error message says you don't have enough credits, you may want to check your account. Or this may be just a glitch with the test procedure and you may want to just proceed with the Zap and see if the actual run is successful.
As an alternative, you may want to switch to Verifalia instead, which not only includes daily credits even with its free plan but also allows to verify lists of email addresses through Zapier (in addition to single email verification).
Verifalia integrations: https://verifalia.com/integrations
Verifalia Zapier integration: https://zapier.com/apps/verifalia/integrations
Disclaimer: I work for Verifalia and have developed its Zapier integration.
Related
I have my own bot running locally and have made it publicly accessible using ngrok
Trying to use the sandbox environment of gupshup to communicate with my bot.
Have hooked my bot using webhook (link your bot)
Have also created a BOT and configured the webhook as a callback POST to my ngrok server.
However when i try replying to a user supplied whats app message after say about 10 min using the Delayed response strategy i.e. by passing the contextobj and message via the send API (http://api.gupshup.io/sm/api/bot/{botname}/msg), I get an error stating "User Not Opted In".
Why isnt the user considered as an Active User since the messaging was initiated by the user and the send API is only replying to that message with 24 hrs ?
How do i simply give a delayed response to the user within 24hrs without forcing the user to opt-in ?
We do this all the time, however we are using the endpoint documented here:
https://www.gupshup.io/developer/docs/bot-platform/guide/whatsapp-api-documentation#OutboundMessage
You have to take the consent of user once before sending messages.
Also while using sandbox the user needs to opt in but for verified user it will be relaxed.
But still you will need to take consent of user at any place (your site, your terms and conditions or anywhere) before sending him anything for the record purposes so that they cannot claim that you are spamming them without consent.
I am busy writing integration tests for Twilio outbound calls.
Code has been written and all works fine, but want to ensure code coverage with tests.
Using Test Credentials provided and phone number: +15005550006 for the from number,
I get the following error: "Unable to create record: The source phone number provided, +15005550006, is not yet verified for your account. You may only make calls from phone numbers that you've verified or purchased from Twilio."
I have verified that I am using the test credentials to make the API call.
I was no able to reproduce the issue. Are you using a non-trial account? If you are, my recommendation would be to open a ticket at help#twilio.com for further investigation of the issue, along with the full details to reproduce the issue.
How To Use Twilio Test Credentials with Magic Phone Numbers
I have a project in TFS. The last two pull requests, we got emails for "xxx has approved the code" but not the subsequent emails for "xxx marked the pull request as completed" The pull requests in question were both approved and completed. The emails do not appear to have been caught in Outlook's spam filter.
The subscription for all projects is "A pull request I created or am a reviewer on is updated"
Version: 15.117.26714.0
Is there a way to diagnose why TFS email notifications are so flaky? This isn't the first complaint I've gotten about TFS email notifications being unreliable.
Have tested TFS 2017.2 instance but could not reproduce the issue on my side. Both approved and completed E-mail sent correctly.
So the issue seems not be able to stable reproduce. For now, there is no way to trouble shoot this directly. You could check the event log in TFS sever to see if you got any error or warning info there.
To narrow down the issue, you could analysis both address the E-mail achieved and sent.
Notifications are sent to your preferred email address, which you can
change from your account preferences. Change the preferred one
and use another to see if issue still exists.
The received notifications are sent by the configured SMTP
server. Try to specify another SMTP Server and the email address
to use for sending emails.
One possibility for this issue, the action of approved and completed pull request were too closely. This may cause TFS only trigger one E-Mail. Do it slowly and try again. Based on my testing, in this case, the E-Mail are sent not in sequence, the completed came first then the approved one.
Moreover, you could also explicitly add a subscription with "A pull request I created or am a reviewer on is updated" just for the project you are working on, which may do the trick.
I am using Paypal REST api to create subscription plan and subscription agreement. I am able to create subscription plan and credit card but not able to create agreement. Whenever I request it gives internal server error.
I am using ruby gem paypal-sdk-rest
Credit card I am using is
4012888888881881
And mode is Sandbox
the Response I am getting is
Response code = 500. Response message = Internal Server Error.
Response debug ID = ea61a34e9fa73
Thanks in Advance
It happens because of frequently used test Credit Card like the one you are using, if you are use different one for this it will help you to solve this issue...
Or may be below one cause of the error
Sandbox Personal Account being used was invalid. The sandbox personal account is causing all this error 500.
HTTP 500 is caused by an internal error. One of the possible root causes is what JIGNESH mentioned.
Can you please open a Github issue with the information you provided here? It is a better place to discuss this kind of issue.
Also, would you explain how you are using subscription? Ruby REST SDK does not yet support the feature, although it is coming soon. Did you add it yourself?
I'd appreciate any help with this, I've run around in circles trying all sorts of combinations with the PayPal Api - but I'm hitting a brick wall on this one.
I'm looking to call the CreateBillingAgreement method but each time I do it fails and reports a 10001 'internal error' from paypal in the response.
I have a valid token and I'm using version 84.0. I've successfully called SetupExpressCheckout and DoExpressCheckout, both of which succeed and the payment goes through. I'm setting up a future payment / pre-authorisation on the SetupExpressCheckout and the user agrees to that no problems.
​Do I need to change settings on the merchant in the sandbox? Am I calling things in the wrong order maybe? (SetExpress, GetExpress, DoExpress, CreateBilling)?
​I'm looking to use this billing agreement to allow a reference transaction in the future. I'm having a test account 'pay' using paypal and not forwarding any credit card details, the payment is for a digital service with no delivery (no shipping is set, no addresses or delivery costs are involved). The overall goal is to provide a one-click re-order button, whereby no details need to be entered by the customer.
I'm using the C# api in asp.net 4, or more specifically I've created Service References from the paypal sandbox wsdl and I'm using those in asp.net.
​Any and all help is appreciated - thanks.
​Russell.
You don't need to call CreateBillingAgreement if you're specifying billingtype MerchantInitiatedBilling in your SetExpressCheckout and DoExpressCheckoutPayment API call. CreateBillingAgreement is only necessary if you don't want to call DoExpressCheckoutPayment.
If MerchantInitiatedBilling is set, DoExpressCheckoutPayment will already return a billing agreement ID, which you can use in DoReferenceTransaction.
I don't have access to an example at hand, but will update this post as soon as I've found one for you.