Hello! I’ve been using a scenario to pull time entries from Toggl Track into a Notion database for the last several weeks. The scenario runs every morning, and has been running without error or intervention. As of this morning, it didn’t run but didn’t seem to produce an error code.
When I looked at my Connections list to try to troubleshoot, the Toggl connection was listed as needing to be Verified. I clicked the button to verify it, and it popped with an error saying I needed to reenter the API. Doing so ended up with the same error again:
Integromat account error: 418
I also tried to reinstate the connection from within a Scenario (which is now prompting me to connect it to my Toggl, as the connection is no longer there), and I’m getting the same error from that method. I also updated the API key in Toggl and tried with the new one - same result.
It’s really problematic if I can’t get this working somewhat quickly. Any help you can provide to point me in the right direction would be incredibly helpful!
Have you tried to delete and re-add the connection to Toggl?
For technical issues or bugs like this, directly contacting support can often lead to a faster resolution. They have access to your specific account details, scenario and scenario logs, server-side logs, and internal tools and resources, which allows them to investigate more thoroughly than what you have access to. Additionally, sharing sensitive information about your situation might not be suitable for an open forum discussion.
You can open a new ticket here, or if you are unable to login for some reason, you can create another new free account to access the ticketing system (which is only available to logged-in users).
If you manage to get your issue resolved with support, we’d still love to hear about it! Sharing your solution on the forum can help others facing similar problems.
Thank you for the suggestions! I did try to delete the Toggl connection, and the error message as I try to reconnect with it is the same error message as before.
I was able to establish a Connection with Toggl Plan… which is a service I don’t use and didn’t think I had an account with. Is it possible Toggl has reorganized their data so it’s all under one umbrella or something? (The Toggl Plan connection asked me to use my Toggl login to connect, which I did and it worked. The Toggl connection on the other hand wants me to paste in my API code and that’s the only way to verify the link between them.)
I’ve created a support ticket and will definitely report back here when I hear a solution. I’m happy to try anything else you can think of in the meantime to troubleshoot this one!
My Toggl trigger returns the error “[400] “Invalid end_date format”” and when I try to connect again Toggl & Make trough the API code Make returns “error 418”…
This is EXACTLY what happened on my end. I continue to get the same error (418) when I try to reconnect via the API code.
I’m sorry it’s happening to you as well, but I’m honestly relieved that it’s a system thing and not a me thing? I couldn’t figure out what I had done to change the functionality! It sounds like the issue has been passed along to the devs so hopefully we both hear back with a resolution soon!
I wanted to let you know that we’ve reported this issue to our dev team, and they will look into it as soon as possible.
We sincerely apologize for the inconvenience caused.
I’ll keep an eye on this issue and I will update this thread as soon as I have any news. If you’d prefer email notifications, please open a support ticket, and our team will keep you informed about the progress.
Thank you very much for your understanding and patience.
We’re still experiencing problems with making a new connection from Make.com to Toggl API (it’s throwing the same error as above: “The request failed due to failure of a previous request.
Integromat account error: 418”)
Also when using the Get Summary Report" function, the output is returning wrong information based on the TogglClientID/Start/End dates - only a small portion of the appropriate data is returning - even though the data is showing fine from Toggl.com and was showing up fine 1 month ago (I realize this last issue may be more of an issue with Toggl’s API call than Make.com).
Unfortunately I’m still experiencing errors. There has been no update to the support ticket either.
It would be wonderful to get an ETA on a fix (i.e. is looking into it as soon as possible = working on it now? working on it next? will get to it whenever we can?) or at least a typical time range for this type of fix. This is a crucial part of how I communicate with clients, and if a different solution is needed I’d rather get started on that now rather than waiting for a fix that might be a long time coming.
@Michaela - is this something that could be provided? (Knowing of course that an ETA or typical time range isn’t a guarantee of a fix on a certain date)
I understand that not knowing an ETA is frustrating, but unfortunately, I don’t have any additional information to share at the moment. As soon as I have an update on the progress, I will make sure to post it here.
Once again, we apologize for the inconvenience and any disruptions caused.
Thank you very much for your patience and understanding throughout this process
the error 400 code issue is the same thing that happened to me for make to gmail, apparently, the gmail was in trial and not production mode and then even i reauthenticate , i get now 403 error. really dont know what is the issue
We faced the same issue and error code in our system and the reason it stoped working is that the toggle connection is using old API and toggle disabled it.
For technical issues or bugs like this, directly contacting support can often lead to a faster resolution. They have access to your specific account details, scenario and scenario logs, server-side logs, and internal tools and resources, which allows them to investigate more thoroughly than what you have access to. Additionally, sharing sensitive information about your situation might not be suitable for an open forum discussion.
You can open a new ticket here, or if you are unable to login for some reason, you can create another new free account to access the ticketing system (which is only available to logged-in users).
If you manage to get your issue resolved with support, we’d still love to hear about it! Sharing your solution on the forum can help others facing similar problems.
I wondered if it was something like this, but couldn’t find info about the date of the switch that made sense so I wasn’t entirely sure.
@Jaroslav_Hejlek Were you able to figure out a workaround / a way to re-establish a connection with Toggl? Or are you also just waiting for Make to figure out a fix on their end?
Getting this Integromat error too, tried setting up a connection with a new make account but can’t. For sure seems linked to the Toggl V8 deprecation, hope it’s sorted soon.
Getting this as well. Hope this gets fixed soon. Before that happens, a more informative error message than “Integromat account error: 418” would be helpful (how about "Toggl API is temporarily deprecated, we’re working on a fix? link to this discussion)
I’m evaluating Make at my startup - and Toggl functionality was the first thing I had hoped to set up. It’s been over a week for this outage, and it’s starting to make me uncomfortable with adopting Make.
Does you company list average outage duration? If I’m integrating with a dozen or two services, how many things will be broken at any given time and for how long?
