Toggl/Notion sync issues

[Cristobal_Alarcon]

UPDATE 1: New Issue

Now, for some reason, the workflow is detecting and sending to Notion time entries when I’ve barely started them, when it should detect them only when I stop the entry timer. I’m confused! Now it really isn’t doing what I need it to do.

How to get a Toggl time entry if I had no internet connection?

Please bear with me; I have practically zero coding knowledge. It seems that if I create a Toggl time entry (in the Toggl desktop app) while I have no internet connection, then reconnect, that time entry won’t go to my Notion database. I attempted to manually sync the Toggl app, but nothing happened. It works just as intended when I have an internet connection, though, with time entries created when I had internet as well.

What is the error message (if any)?

No error message.

Please share the workflow

Share the output returned by the last node

Output from the New Issue

[
{
"id":
"b12c54f0-dcbc-4b0c-9a6e-302851b73065",
"name":
"relaxing 3",
"url":
"https://www.notion.so/relaxing-3-b12c54f0dcbc4b0c9a6e302851b73065",
"property_task_end":
1670913060000,
"property_task_start":
1670913000000,
"property_minutes":
27848551,
"property_started":
"2022-12-13T06:31:00.000Z",
"property_horas_total":
0,
"property_":
true,
"property_tiempo":
"0hr 1min",
"property_horas":
0,
"property_start":
{
"start":
"2022-12-13T03:30:00.000-03:00",
"end":
null,
"time_zone":
null
},
"property_projecto":
[
],
"property_end":
{
"start":
"2022-12-13T03:31:00.000-03:00",
"end":
null,
"time_zone":
null
},
"property_last_edited":
"2022-12-13T06:31:00.000Z",
"property_override_start":
{
"start":
"2022-12-13T03:30:00.000-03:00",
"end":
null,
"time_zone":
null
},
"property_tarea":
"relaxing 3"
}
]

Information on your n8n setup

• n8n Version 0.204.0
• Database you’re using (default: SQLite): I don’t know
• Running n8n with the execution process [own(default), main]: I don’t know
• Running n8n via Desktop App

[Jon]

Hey @Cristobal_Alarcon,

Welcome to the community

Looking at the node it looks like the issue could be with how we detect new events, We set the start date to be the time the workflow last ran from so when it comes to offline events if the start time is saved before the run after the run has happened it won’t get picked up which isn’t ideal.

I suspect the second issue is also related to this, I will get an internal dev ticket raised to look into this more.

[Cristobal_Alarcon]

Ok! I don’t know if it helps but is it possible check the code of Make (Integromat) and see how they handle this kind of tasks? Since they are open source maybe that’s something you can access to. So you don’t have to start from the ground.

[Jon]

Hey @Cristobal_Alarcon,

I was fairly confident that Make / Integromat was not open source. I have an idea on how we can handle this already which would be to redo the node to use the newer webhook options in Toggl rather than polling this would then set Toggl to post to n8n when an event occurs.

The downside to this though it will require a bit of work and we will need to wait for the internal resources to be available to handle it. For now as a possible work around could be to see if a webhook can be manually created in Toggl and point that to an n8n webhook URL and from there you should be good to go.

[Cristobal_Alarcon]

Oh my bad, I confused it with Toggl being open source.

About the webhook. Everything was fine until Toggl asked me to use an URL endpoint. I have no idea what that is, so I searched on google on how to create one, and boy I’ve hit a wall. It seems that you need programing and software skills for that, and I have none of them. Guess I’ll have to wait for the n8n team to find a workaround.

I’ll keep using Zapier in the meantime, but I’m heavily invested in n8n.

[Cristobal_Alarcon]

Just found out that Zapier does this job properly, about this

Now, for some reason, the workflow is detecting and sending to Notion time entries when I’ve barely started them, when it should detect them only when I stop the entry timer. I’m confused! Now it really isn’t doing what I need it to do.

It adds time entries only when you stop the timer. I thought it might be helpful.

[Jon]

Hey @Cristobal_Alarcon,

I suspect they use the webhook option which allows for subscriptions so when an event is started or ends it gets a message to then process the item. This is part of the change I have requested internally, The problem with this isn’t that we don’t know what to do it is finding time to assign resource to it and that tends to be based on what we are currently working on and how popular the node is.

It could be that we get to this in the next couple of weeks or it might take a bit longer.

[Cristobal_Alarcon]

Awesome! I’m a free user, so I can’t really be bothered by the time if it gets implemented or not. I appreciate the consideration about keeping us informed about the internal request, though.

I found another feature that could be useful. I’ve been using Zapier lately, but I wanted to try something with the N8n module right now.The thing is, when I activated it, it fetched the time entries that I had created so far and created new items in my database. This could be convenient in some cases, but in my case, it created duplicates of already existing database items.

Integromat solves this by providing a field in which you can specify the date forward from which time entries should be checked.