How automation is transforming certified communication

Automation goes far beyond sending emails

When companies think about “automating communications,” they usually imagine an API that sends emails automatically.

But in the realm of certified communication, automation happens elsewhere: in the integration of traceability, certification, and delivery statuses within client systems.

The goal is not to send an email faster, but to make evidence-based decisions, synchronize statuses, activate internal flows, and ensure that every legal communication is recorded in a verifiable way.

That’s why, in eEvidence:

• There is no API for sending emails.
• The client sends from their usual system (SMTP), without altering their processes.
• Automation happens afterwards, thanks to evidence queries, event publishing, and real-time integration.

API: automation based on certified evidence

The eEvidence API allows client systems to access at any time the exact status of each communication:

• Sent
• Delivered
• Not delivered
• Certified
• eEvid available

Additionally, it allows downloading certificates automatically to archive them in the ERP, CRM, or document management system.

This enables automating flows such as:

• Collections: send reminders only if the previous delivery appears as “delivered”.
• Onboarding: advance to the next phase when delivery evidence is available.
• HR: automatically register that a notification has been made available to the worker.
• Compliance: maintain updated audits without manual intervention.

Automation no longer depends on sending: it depends on what happens afterwards, and how the client’s system reacts to that information.

AMQP queues: real-time events for high-volume clients

For clients managing thousands or millions of communications, eEvidence offers dedicated AMQP queues (FIFO) where we publish events in real time, such as:

• email received by eEvidence
• delivery confirmed
• delivery failed
• open tracking

This way, internal systems can act immediately, without the need to continuously query or poll.

Examples:

• An anti-fraud system blocks a process if a critical notice has not been delivered.
• A financial platform automatically records when a regulatory notification has been made available to the client.
• A logistics system updates the status of a shipment when the communication to the recipient is certified.

Why we don’t offer a sending API (and why it’s better this way)

This is a very important point.

Unlike other services, eEvidence does not offer an API for sending emails. And this is deliberate:

• Sending via SMTP is universal and works on any platform, language, and system. If you have the capability to implement an API, you also have it to implement a flow against our SMTP servers.
• It doesn’t require modifying internal processes or communication issuance systems.
• It avoids dependency on a proprietary API.
• It reduces risks: if the API fails, sending continues to work exactly the same.
• It guarantees maximum compatibility with any corporate server, cloud provider, or SaaS platform.

eEvidence integrates after sending, converting an ordinary email into a certified communication with verifiable traceability.

Automation is in the probative back-office, not in issuance.

Frequently asked questions (FAQ)

Can I send emails via your API?

No. Sending is always done via SMTP from client systems. The API is oriented to query evidence and synchronize statuses.

How do I receive events in real time?

Through API queries, via dedicated AMQP queues, or through a webhook if agreed upon in the project.

What are the advantages of not using a sending API?

It avoids dependencies, works with any existing system, and guarantees universal compatibility thanks to the use of the SMTP protocol.

Do I need to change my ERP or CRM to integrate with eEvidence?

Not at all. Email sending depends on the client, and it’s enough to implement the status API or AMQP/Webhook events to automate traceability.

Conclusion

Automation in certified communication is not about sending emails automatically, but about integrating probative traceability in real time into the company’s internal systems.

Thanks to the query API, AMQP queues, and webhooks, eEvidence enables:

• synchronizing statuses,
• automating internal decisions,
• updating audits,
• and recording evidence without human intervention.

The combination of universal sending (SMTP) with certified and automatable traceability makes eEvidence the most robust infrastructure for legal and transactional communications.