With the Capacities email integration, you can save formatted messages, images, or files to Capacities from your inbox. You can of course also forward emails to Capacities.
You don't have to set up anything to use this integration, just use the email address you signed up with. If you want to add additional email addresses open the Capacities app and go to "Account > Settings > Integrations > Email" and follow the instructions there.
How it works
Simply send an email to firstname.lastname@example.org from the email address you signed up at Capacities. It will be appended to your daily note as a "Toggle" Block with an email icon. Just click on the toggle to open it.
You can send formatted emails. You can use all Capacities shortcuts:
1.for numbered lists
**text**for bold text
*text*for italic text
Standard markdown formatting is supported as well.
To add tags to your message simply use the
# symbol. Capacities matches your text with your existing tags or will create new tags.
❗️ Rules for tags
- You cannot use special characters in your tags.
- Tags will automatically be transformed. So if you have a tag called
Cognitive Biassimply add
#cognitivebiasto your text, and it will automatically be matched.
Linking and creating content
You can create new objects and link existing content from your email. Use the following syntax inside the body of your email (not supported in the subject line):
to link to a page with the title "Wendelstein reactor". If this page exits in your space it will create a link to it, otherwise, a new page will be created. This works for all content types in your space. If you have a content type
Person you can link or create it by using
Note that this will only create a link to a new or existing object. It will not insert the content of the email or the subject line into the linked object.
You can use this at the beginning of a paragraph to create a new block link for that object or somewhere in your text to create an inline link to that object.
Alternative ways of "create or link" are
+person/Steve Jobs/ and
@person/Steve Jobs/, similar to the syntax you can use in the app.
If your content type contains space characters, like "Book Summary" you need to specify it in upper camel case format:
If you only want to link and not create you can do this by just referencing the title:
Saving web links
If you want to save a web link, paste the web link into a new line. If you want you can add tags with the
# symbol after it:
https://capacities.io #pkm #note-taking
The web link will be tagged and saved to your web links database as well.
Saving images and files
If you send images or files as attachments. They will be added to your daily note.
Saving code files
If you send a code file, for example, a Typescript or Python file ending with the corresponding extension it will automatically be transformed into a code block that you can continue editing in Capacities.
Saving markdown and text files as pages
If you attach .md or .txt files to your email they will be saved as pages in your space. The file name will be used as the title of the page.
Using the subject
The subject will be added as the title of your note.
If you want to save an email to a specific space other than your selected default space you can add the space number, here the third space, based on the order of your spaces in your home dashboard.
/3 My email subject
Furthermore, you can add tags to your note with the
My email subject #hashtag
All emails you forward to Capacities are not sent to a classic inbox. Nobody working at Capacities has an inbox for
email@example.com. It's only a programmatic queue where all emails are held for a short period of time. They will be processed by our servers once they get received by the queue and are redirected to the corresponding space based on the email address they were sent from. After an email was added to your space it will be deleted from that queue. If you want to read more about privacy in general visit this page.
🤔 Do you find this explanation unclear or feel like something is missing in the docs?
With your help we can make the docs better for everyone. So just let us know, and we’ll improve it ASAP!
📨 Did reading the docs make you think of any product improvements?
Please let us know if you have an idea for a feature, think that something is missing or see a conceptual inconsistency that could be fixed. Just post it on our feedback board and discuss it with us and other users!