I am making a get request using a Zapier webhook in my Zap to the Zoho Invoice API at the URL https://invoice.zoho.eu/api/v3/invoices/{invoice_id}. I am passing the invoice ID retrieved from the previous step in the Zap (another GET request to the Zoho Invoices API) but it returns the below error.
Failed to create a request in Webhooks by Zapier
The app returned "Please ensure that the invoices has less than 100 characters.".
When making the GET request locally using postman it returns Status 200 OK along with the invoice data object.
I have searched the Zoho Invoice API documentation for this error message but find no reference to it, neither does the Zapier interface display what Status code is being returned, so I am struggling to diagnose this.
If anyone can help it would be much appreciated.
I got this to work using the Catch Raw Hook event of the Zapier webhook app rather than the standard 'Catch Hook'.
Related
I'm attempting to retrieve the "success_url" from a charge in Stripe via Zapier.
When using the Webhook step within Zapier, I get the following error:
The app returned "Missing required param: success_url.".
In the backend of Stripe, I'm able to view this session and confirm that it indeed does have a success_url specified, and the checkout process even brings the customer to the url correctly, but I still get this error within Zapier.
Am I missing something??
All I'm trying to do is retrieve that success_url so that I can email it to the customer after the transaction.
Which endpoint are you using to retrieve the success_url? Viewing the Stripe API docs, it seems the success_url is retrieved with a session ID:
https://stripe.com/docs/api/checkout/sessions/retrieve
The GET on the charges endpoint does not appear to return this ID:
https://stripe.com/docs/api/charges/retrieve
Perhaps you could share a screenshot blocking off any sensitive (API keys, PII, etc.) of the request?
I have created a post api and did put that post api inside the event webhook settings of sendgrid. But when i enabled it and check the json response on my api in local, i am getting fake messages and not real data.
Anyone know whats the reason. I checked their documentation, it is not telling anything else.
Source of information : https://sendgrid.com/docs/for-developers/tracking-events/getting-started-event-webhook/
If you are using event webhook according to above documentation in the question. You wont get the real data as for testing purpose sendgrid sends that data from your account. Instead try implementing the API. Then you will get the real response as it would contain your sendgrid api key.
Is it possible to request from the API to resend a webhook?
From here i can see this is possible from the Admin Panel
https://www.docusign.com/blog/dsdev-adding-webhooks-application/
When a webhook request fails, the Failures screen also enables you to
resend the notification. This can be very helpful when debugging your
listener software.
I want to do the same but from the API.
Thanks!
You can use the ConnectEvents Api's.
Specifically the following api's
retryForEnvelope
Republishes Connect information for the specified envelope.
retryForEnvelopes
Republishes Connect information for the specified set of envelopes. The primary use is to republish Connect post failures by including envelope IDs for the envelopes that failed to post in the request. The list of envelope IDs that failed to post correctly can be retrieved by calling to [ML:GetConnectLog] retrieve the failure log.
I have a web service that creates Docusign envelopes with a PDF that needs to be signed. On my test environment, after the envelope gets created I query for the envelope status, as well as the recipient status. When using the API call, the respondents with bad email addresses have the status "autoresponded".
Now on my Docusign Connect implementation, I have two separate routes that get hit. One for when the email gets successfully sent or if the request is completed, and another one specifically for email delivery failures. When I had a single route, none of the recipients were marked as "autoresponded" like the API call returned (the API call result ends up being returned before the Connect implementation gets hit by Docusign).
After splitting them apart, I expected the email delivery failure-specific route to have the correct signature status. Unfortunately when this route gets hit, all recipients have the status of "Sent", regardless if their email is valid or not.
I'd contacted Docusign a while ago and their response was the number of events a single Connect implementation was listening for. By that assumption, this delivery failure-specific route should be getting a status of "autoresponded" like our API call is receiving, which doesn't seem to be happening. How can I get the Connect implementation to return the correct recipient statuses?
Every time I've opened a support ticket on their website, the corresponding account can no longer log in, meaning it's always a one-way communication to their support team. Has anyone gotten around this issue before?
My thought is that if the email failure route gets hit, flag that account as having a bad email address for one of the recipients and force the user to log into their accounts to see the actual status. Another option would be to query the API for that envelope's status, however I feel like a lot of delivery failures could easily trigger the max number of API calls.
Posting an answer, the original poster figured it out in the comment, but here is the answer for everyone else per Ricky Story:
"Return Recipient Auto Responded Status in Connect/API" that DocuSign Support should be able to enable.
To do that you would need to contact the DocuSign Customer Support and request them to enable this option.
Can anyone please tell me (or point me in the direction) how to generate an invoice email using webhook api in stripe with the mailchimp account?
You actually can't do that directly because you can't create a MailChimp endpoint which receives data through the web. You need an intermediary layer in between Stripe and MailChimp, which receives data from Stripe, validates the data, converts the data according to your needs, and using MailChimp API sends it to MailChimp to be sent out as an email. But an easier approach will be (in my opinion) creating an in-house solution for sending out emails instead of using MailChimp.