Skip to main content

Email Pipelines

Updated over 3 weeks ago

πŸ”’ Permissions
​

  • Who can create email pipelines? The system administrators.
    ​

  • Who can use these pipelines? Generally anyone who knows the email address, subject to options linked to publication rights.
    ​


To facilitate contributions via email, Elium suggests a generic email address available to all users. This allows users to transfer emails or create new ones, including attachments, to save them on the platform.
​

In addition to this generic address, other email addresses can be created following specific publication rights and made available to users.
​

It is also possible to generate email addresses aimed at:
​

  • saving the email and attachments that reach the platform (similar to the standard email address, but with personalized choices regarding publication rules)
    ​

  • saving only the email
    ​

  • saving only the attachments (files)
    ​

  • transforming the email into an article (the subject of the email becomes the title, the body of the email becomes a text block, and any attachments are listed in a 'gallery of files' block)
    ​

  • transforming every web link content into the full body of the email
    ​

Every email address is differentiated by an extension defined by the administrator: your-platform.elium.com+extension@in.elium.com
​

These unique email addresses have distinct publication rules:
​

  • the publication space
    ​

  • the tag(s) attributed to the generated content
    ​

  • the contributor
    ​

  • as draft or published
    ​

  • with or without verification of the publication rights of the sender
    ​

  • with or without confirmation of receipt by email
    ​

Creating Contributions via Email Address

To create these addresses, navigate to the administration interface and select the 'Email pipelines' tab.
​

  1. Create a new address.
    ​

  2. Define the extension to be used (we recommend making it sufficiently explicit).
    ​

  3. Describe the behavior of this pipeline for quick reference in the interface.
    ​

  4. Define the contributor: you can either let the system attribute the content based on the sender's email address or force attribution to a specific user.
    ​

  5. Specify whether the system should verify if the user has the right to publish content in the selected space.
    ​

  6. Indicate whether the system should generate a confirmation of receipt.
    ​

  7. Define how the system should handle sent content.
    ​

  8. Choose the publication space.
    ​

  9. Specify any tags to be applied.
    ​

  10. Tick the option if you want to publish the received content immediately.
    ​

Restraints and Limitations of Email Pipelines

  • Every email address operates uniquely, potentially leading to numerous addresses.
    ​

  • To save it as an article, emails with overly complex layouts may not be replicated optimally.
    ​


πŸ‘ Pro Tip
​

  • We recommend always properly numbering the files you send by email (by default, their name is used as the title in Elium).
    ​

  • Enable confirmation of receipt whenever possible to ensure that the content sent has been received.
    ​


Did this answer your question?