I want to let google sheet catch webhooks and populate cells with the webhook content.
But no cells are being populated and in the executions menu i see for instance this:
Version 3 doPost Web App Oct 23, 2021, 12:47:30 AM 0.235 s
Failed
i have tried a few scripts but i keep getting this error.
I dont know if this error is because all the scripts are wrong or if there is something else not working.
When i sent the webhook commands to a test url of webhook.site i do see that it receives it and i also see the contents there. So on the sending side things seem to be working good.
this is one of the scripts that i tried:
https://gist.github.com/AvlSEONinja/b59386a06811f7d29061870195d3ee5a
It goes with this youtube tutorial:
https://www.youtube.com/watch?v=rHzb0rXiP7o
In my case its not used for elementor, but it was the only example that i could find of letting google sheet catch some strings via webhook and put it into cells.
My webhook consists of 5 lines about 30 characters, and i want each line in a cell and per received webhook a new row.
Related
I'm running an A/B test in Firebase. The client is getting values and responding appropriately. I can see "current users" in the live view:
But even after 48 hours I still see "Running (0 users exposed)" in the headline of the experiment.
How can these be "active experiement users" yet not show up as part of the experiment?
For comparison, here's the staging build of the app, which has assigned users with the same code, just building with a different scheme and hitting a different Firebase app:
We call fetchAndActivate on launch:
FirebaseApp.configure()
RemoteConfig.remoteConfig().fetchAndActivate { _, error in
print(error ?? "Fetched!")
}
For now, it happens (no data in Firebase remote config A/B test experiment) if you have an activation event configured for A/B test experiment.
Check these:
If you have 2 different experiments, both will fail to get results even if you have "activation event" configured only in 1 of them.
Additionally, remote config will not work as well, you'll be able to get only default values.
it takes many hours before you can see any data in your experiment, wait for at least 24 hours. It will show 0 for many hours after the start.
make sure your users have the version of your app with the latest SDK.
Since your experiment is with Remote Config: When activateFetched() is called, all events from that point on will be tagged with the experiment. If you have a goal or activation event that happens before activateFetched(), such as automatic events like first_open, session_start, etc., the experiment setup might be wrong.
Make sure to call fetch() and activateFetched() before the activation event occurs.
The good way to check if your experiment is working now is to set it to a specific version you didn't publish yet and check logs from remote config with the fresh app install(or erase all app data & restart). It should show different variant every time you reinstall the app, since your Firebase Instance ID changes after app reinstall/app data erase.
If you see variants change - then A/B test is running well.
I'm building an Outlook Add-In and using the Outlook REST API 2.0. When updating a mail message to flag the message for follow-up, the update is accepted and in the Outlook Web client it briefly shows the start and due dates, but within a few seconds the start date goes away. When looking at the message through the API, the start date is completely removed, even though it was successfully added.
The API is PATCH Office.context.mailbox.restUrl + '/v2.0/me/messages/' + messageId ...
EDIT: I confirmed that this same behavior is exhibited in the Graph API as well.
As soon as the API is called, the UI on the message is updated:
Shortly after that (sometimes within a second, sometimes a little longer), the UI changes to:
And once the UI updates, if you query the API for the message and look at the Flag property, the StartDateTime object is completely gone.
Has anyone seen this or know why it might be happening?
Checked it on Graph with the following payload for PATCH-Message call and it seems to be working fine.
{"flag":{"dueDateTime":{"dateTime":"2020-08-20T00:00:00.0000000","timeZone":"Asia/Kolkata"},"flagStatus":"flagged","startDateTime":{"dateTime":"2020-08-14T00:00:00.0000000","timeZone":"Asia/Kolkata"}}}
I suspect that there is another application/outlook add-in that's removing this flag. Can you check once?
I'm creating an Applet that will trigger as follows:
If New row added to, then Send an email from myemail#gmail.com
This is Applet version ID 100348625.
Notice the "to," which sounds to me like a bug. I've verified that everything is done properly and still this applet is never triggered. I'm adding rows to the spreadsheet and nothing happens. The applet says "Never run" so it doesn't even attempt to do it. It's like the adding of the row isn't being detected by IFTTT.
The spreadsheet contains an email address for the destination. The body of the email is long but within the maximum. I'm connected to my Google account for both the Google Sheet and Gmail services. My spreadsheet URL is good. I've tried both the internal URL and the Shared URL. I've also tried with the path and name instead of the URL but the same result.
What am I doing wrong?
I replicated your issue and I have managed to find a workaround, using Mail, instead of Gmail. When using the Gmail as that I got exactly the same result as yours - my applet was never triggered. Then I did it anew with Mail as that, and it started to trigger right away, sending me a bunch of notifications on each edit/row added. But the emails I receive are from "Google Sheets via IFTTT" which is action#ifttt.com instead of my own email.
Then I figured that something is probably wrong with the service and I headed to the services outage page of IFTTT which is located here. As of the time of this answer, one of the issues states:
Gmail actions may fail for some users Incident Report for IFTTT
Identified
The issue has been identified and a fix is being worked on.
It will require a large rework in how Gmail is implemented, we
appreciate your patience as we get Gmail up and running for everyone.
(Posted May 15, 2019 - 16:51 PDT)
This sounds to me like a serious issue, that is probably the explanation of all your trouble. It probably fails silently in the background and it the whole applet never registers as triggered.
Until they've fixed it, I suggest using Mail, instead of Gmail.
Here is how my working version looks:
Hope this helps!
In the end, I had to switch to another solution than IFTTT because this bug is not going to be fixed soon enough. Until it is fixed, I have no choice.
So I went with Integromat and I was able to do my integration work easily.
I have successfully created a client side script function that removes and reinstates all conditional formatting on a templated Sheet (to maintain a prescribed conditional formatting regime without locking cells). I have placed a call to this function in the sheets onOpen() event handler. When in the Script Editor I explicitly run the onOpen handler all works well. When I open the sheet and let the onOpen event run naturally I get an authentication error in response to the batchUpdate call that requests the Conditional Formatting changes:
Execution failed: Request is missing required authentication credential. Expected OAuth 2 access token, login cookie or other valid authentication credential.
1) Is there a logical explanation why the code does not fail authentication when I run the code explicitly from the Script Editor while it does fail in response to the onOpen event firing?
2) I have followed the OAuth 2 links and am a little overwhelmed, can anybody please direct me to a simple set of actions I need to take to allow me to make a client side script work with the Sheets object to which it is attached for all users? Is this a more difficult endeavour than I had anticipated?
Update: I got my code to work in script attached to a spreadsheet. An installable trigger was used to send API batch update requests of Conditional formatting - all good so far. I have a number of spreadsheets that I want to use the script, so I created a version of the script and added it as library to the first "new"spreadsheet. I had to authorize the API in that new sheet but once done the library trigger event fired at the appropriate point. However, despite the API batch update request being written in the context of an installable trigger (in the library file) execution again failed with the original error message:
"Execution failed: Request is missing required authentication credential. Expected OAuth 2 access token, login cookie or other valid authentication credential message.
Precisely the problem the Installable Trigger had solved previously.
What extra steps must I take to avoid this error in a library trigger please?
So I have implemented the Asana Webhooks API as described in their documents. I can pass it a project ID and request a new webhook be created. The API successfully sends a authentication request to my application which returns the Security header as described in the Docs. Asana then returns the expected success response, outlining the newly created Webhooks unique ID.
Now if i take this ID and then query the Asana API to show me all configured webhook's on either the parent Workspace or the project resource directly it returns an empty data JSON Object or reports the resource doesn't exist, suggesting the Webhook Ive just created wasn't actually created, despite giving me the expected success response.
Also If I then make a change to a project it doesn't fire the webhook and I don't receive any events on my application.
Strangely everything was working on Friday but today (Monday) I'm experiencing these issues.
Any pointers would be good, Ive been working as the Docs suggest in terms of my request structure and am authenticating using a PAT, Ive even tried a newly created token.
Thanks,
Our webhooks use the handshake mechanism to make sure that it's possible to call you back, but there's always the possibility that subsequent requests can fail. Additionally (although we don't document this very well - there's an opportunity for us) we should immediately try to deliver a (probably) empty event after the handshake (it looks like {"events":[]}. This is kind of like a "second callback" that contains anything that has changed since you created the webhook.
If this fails - or if any subsequent request fails often enough - the webhook will get trashed. "Failure" in this context means returns HTTP response codes other that 200 or 204.
As for why you're having trouble querying the webhook itself, I wasn't able to repro the issue, so we'd have to dive deeper. It should be fine if you:
Specify the workspace
Optionally specify the resource
I tested this out, and it seemed fine. You also might want to directly query the webhook by id with the /webhooks/:id endpoint - note to use the id of the webhook returned by create, and not the id in the resource field.
If you created the webhook (specifically, your PAT or OAuth app was the one making the create request) you should see the information just fine. If you can get the webhook by id, you should see last_failure_at and last_failure_content fields which would tell you why the webhook was unable to make the delivery.
Finally, if you would like to contact us at api-support#asana.com and let them know more details (for instance, the ID of the webhook you're trying to look at) we can look at those fields from our side to see if we can identify what's going on.