Payments
Cards, deposits, a sandbox you can fail. When a connector ships, it will say who holds the merchant account and who never sees the number. We will not print a card-network logo to look further along.
Four kinds of connection, none sold as live brands
People ask whether Eqlo "has Stripe" or "talks to Google". A logo row would answer the wrong question. This page names four categories we intend to connect: payments, calendar, messaging, spreadsheets. It does not claim a live brand connector. It does not show a vendor mark we do not run.
The four categories
A connection is a job: take money, show a free Tuesday, send a reminder, read a sheet the floor already uses. The vendor you already pay may sit in one of those jobs. Until a connector is live, we will describe the job, not the brand.
Calendar
A week view that is not a screenshot. The diary you already run can stay the source. A live book on a booking site is the product page. A brand calendar sync is a later connector, named when it exists.
Messaging
A reminder the visitor asked for, a note to the owner. SMS, mail, or an app push. We will not list a chat vendor as if a bot were already wired.
Spreadsheets
A sheet the team already opens on Friday. Import is a careful act: pick a region first, refuse a column you should never have pasted. A brand sheets connector is not live on this page.
What this page refuses to claim
Home has a picture that mentions calendars in a filename. That is a marketing still, not a certified connector. Docs will not invent a webhook for a brand we do not call. The customers page will not show a vendor as a "partner" to fill a cell.
If a sales call said "we integrate with everyone", that call was wrong. Write. We will date a correction. We will not add a logo to make the sentence true.
A category is a promise of a job. A logo is a promise of a contract. We will not print the second before the first works.
How a connector will be announced
A dated line on the changelog. A paragraph on this page that names the vendor, the region rules, and who holds the secret. A docs topic after the connection actually runs. Not a silent logo in a footer.
Until then, you can still describe the job in a project brief: "deposit on the long visit", "remind the day before", "read the stock column". The builder can draft screens around a job. Wiring the vendor is a later hour.
Secrets, regions, leaving
A connection that needs a key should sit in the region you picked for the project. Support will not ask you to paste that key into chat. Export should let you leave with the data you brought. Those rules already live on security and residency. They apply before any brand name does.
If a category is the reason you are here
Read the product page that already does the job, or write if a named vendor is a blocker.
Questions about Eqlo integrations
Do you have a live Stripe connector?
We will not claim one on this page. Payments is a category. When a card vendor is wired, it will be named here with a date. Until then, treat any logo you saw elsewhere as marketing stills, not as a contract.
Can I connect Google Calendar today?
Not as a documented brand connector. A booking site can still show a week you type or that comes from a diary you already run. A Google mark will not appear here to suggest a finished OAuth loop.
Will you add a marketplace of plugins?
That is not the plan we are writing. A short list of jobs we stand behind beats a store of third-party tiles we cannot review.
Where do I ask for a vendor by name?
Contact, and put the vendor in the first line. Say the region of the project. We will not promise a date we have not put on the changelog.
Describe the job. Name the vendor later.
Five free projects is the public plan once seats open. Integrations will be dated, not logo-stamped.