Tags added to text in Whatsapp or Telegram does not transform automatically
D
Dietrich Inocencio
I am trying to send links from Edge or Tiktok via Whatsapp and Telegram but the tags do not transform automatically. For example I have a tag for "date places", when I add links with a tag #dateplaces, it creates a new tag "dateplaces" (with no space), instead of my original tag "date places".
Log In
Beth
Merged in a post:
Tags
S
Stefan Imhof
When sending input via Whatsapp I often add a tag, e.g. #mytag
If the tag already exists in Capacitities, a new tag is created with the same name. So like that I end up having the same tag multiple times in Capacities. And it's not possible to merge them to a single tag - what it should be from the beginning.
Capacities
open
Not actively worked on, moved to open for now.
Steffen Bleher
in progress
We're working in resolving this. Tags take a while to get recognized. So if you create a tag #hello and then wait 3 minutes and use it again it should work. We'll work on making the tag data available faster.
J
Junior Ribeiro
Steffen Bleher I don't think the problem is related to availability time. I say this because, when I started using the app a few days ago, the first tag I created to organize myself was "tasks."
As you can see in the image (with an icon), if I create the same tag again, regardless of the time, it duplicates.
The first tag was sent via API, but instead of using the original tag, it created a new one. Every time I send it via API, it keeps duplicating.
Later, I manually marked the same tag in my daily notes.
If you check the next two instances, the tag was sent via WhatsApp. Despite the longer time interval, a new tag with the same name was created again.
I also tested it via Telegram, and it didn't use the existing tag either—instead, it duplicated it.
I believe preventing the creation of tags with duplicate names could potentially solve this issue.
G
Gideon Lichfield
Steffen Bleher I'm having similar issues, but inconsistently so. I created a tag called "ToRead" a few days ago, and it's been working consistently when I send links from WhatsApp and from the Capacities Chrome extension tagged with #toread. But then I created a tag called "Futurepolis links", and when I tag things with #futurepolislinks it creates a new tag in Capacities with that name each time I send. I tried the same with #FuturepolisLinks and the same occurs, with the capitalization. In the screenshot attached, the bottom three examples are things I tagged manually within Capacities; the ones above are all sent via either WhatsApp or the Chrome extension, and as you see from the colors each one is a new tag.
Steffen Bleher
Junior Ribeiro: Thanks for sharing. We'll have a look!
Steffen Bleher
closed
This should be fixed with the latest update. Thanks for reporting.
P
Paulo Fehlauer
Steffen Bleher Just updated the app and tried to send a link through Whatsapp desktop app with #a-processar tag. It created a duplicate tag and didn't add the link (screenshots attached).
Steffen Bleher
Paulo Fehlauer could you try again a bit later? does it use one of your existing tags now?
J
Junior Ribeiro
Steffen Bleher .
P
Paulo Fehlauer
Steffen Bleher I changed the tag to 1 word (#pendente instead of #a-processar) and my API imports seem to be working correctly now, without creating duplicate tags (don't know if that was the reason, though).
In spite of that, Whatsapp and Telegram sharing are still not working. The existing tag is now recognized, but no weblink was created in both trials.
Steffen Bleher
in progress
Luca Joos
under review
We'll look into it, thanks.
P
Paulo Fehlauer
Luca Joos I'm having a similar issue here. I wrote a script that auto-imports Readwise Reader highlights to Capacities via API, applying a "to-process" tag, which I also use in items added via Telegram / Whatsapp, so I can work on them later. It was working fine until a few days ago, but now every item added with either method creates a new "to-process" tag, which basically ruins my entire logic.
K
Kuntal Go
Luca Joos Thank you for addressing this. I would like to propose an enhancement based on a related request I shared on Canny last year.
Currently, text messages forwarded from WhatsApp or Telegram to Daily Notes appear with a prefix indicating the source app (via a small icon) and the time of sending. While this is helpful, it would be significantly more valuable if the timestamp were recognized as a proper time marker (e.g., @time), allowing it to appear in the timeline.
This feature would greatly benefit users like myself who track daily activity logs for productivity review and introspection. At present, timestamps are neither automatically recognized, nor does manually adding @now convert the entry into a timestamp. Enhancing this functionality could align Capacities with other productivity and bookmarking applications that integrate time and location data into their notes, enabling better context and insight.
Moreover, many Capacities users already utilize "Places/Map" objects. Integrating this feature would allow users to tag locations (e.g., @Tokyo, @Mumbai) alongside timestamps (e.g., @now or @7:30 PM), offering a more precise representation of when and where an activity or thought occurred.
Capacities' seamless integration with popular chat and email apps makes it an exceptional tool for capturing ideas and activities. Adding timestamp recognition, whether through auto-detection or manual entry, would further enhance its usability and align it with contemporary productivity tools.
Here is the detailed ticket for this feature request: https://capacities.io/feedback/p/enhancing-temporal-context-recognition-in-daily-notes-for-data-fetched-from-chat