Connectors: link your systems through their APIs
A flow links a source to one or more destinations, with the transformations needed in between: data moves without re-keying.
Technical overview of a completed project, not marketed. La Passerelle was built and validated in-house; no access, purchase or subscription is offered. See the work.
The principle
- A source: a system that produces data (an order, a contact, an event);
- transformations: adapting the format, filtering, grouping, calculating;
- one or more destinations: the systems that receive the data.
Each external system is attached through a connector, which handles communication with its API.
Available connectors: Slack, Discord, Microsoft Teams, Google Chat, email (Brevo), Airtable, HubSpot, Intercom, Zendesk (ticket), Pipedrive, Google Sheets, SFTP, WhatsApp (free-form message or template), email to members and generic HTTP request, plus your organisation’s custom connectors. Transformations offered: filter, fields, mapping and Python script.
In pictures
Content erased after processing
La Passerelle passes data from one system to another and erases the message content after processing (7 days after a failure so it can be retried, 24 h in debug mode). The history is kept 30 days. See security and data.
Credits
In the model studied, credits were used as you go: 1 unit = 1 script step run, or 3 successful sends. Filters and fields are free, and a failure costs nothing.
Frequently asked questions
Do I need to know how to code?
Not for common cases: filters, fields and mappings are set up in the interface. A free-form Python script, run in an isolated environment, remains possible for special cases.
What happens if a system is unavailable?
Sends are retried automatically over 12 hours (at 1, 5, 15, 60, 180, 360 then 720 minutes). Beyond that, or on a definitive refusal, the delivery is abandoned and can be retried for 7 days. After 10 abandoned deliveries in a row, the destination is suspended and administrators are warned by email.
Can I connect an application that has no connector?
Yes: with the generic HTTP request connector (POST, PUT, PATCH; JSON, XML, SOAP, form, CSV, text or custom body) or with a custom connector of your organisation (draft, real test, publication, rollback).
Going further
A similar need?
I design custom integrations and tools: describe your need in a few lines.