Integrations
Connect RUAL to the services you already use: payments, mail, messaging, AI, cloud storage, shipping, accounting and single sign-on.
Keep credentials out of the canvas Where a service has one, set its keys up as a service provider: the cluster holds them, and a block only names the provider. New here? Third-Party Integrations covers calling APIs, receiving webhooks and handling failures.
Sign-in
Payments
Messaging and notifications
AI
Cloud and servers
Databases and search
Maps and places
Shipping and logistics
PostNL Request barcodes and labels, calculate delivery and shipping dates, and find pickup locations. Floriday Open a Floriday connection and call its API with the custom request blocks. NS (Dutch Railways) Read live departures, arrivals, disruptions and stations, and find the nearest station.
Accounting and finance
Twinfield Connect with OAuth 2.0, create and read invoices, read journal transactions and list offices. EDIFACT Parse EDIFACT files, including PRICAT, and format an object back into EDIFACT.
Developer tools
Apps and devices
Printing and hardware
Frequently asked
Which services does RUAL integrate with?
Payments such as Stripe and Mollie, mail such as Postmark, mssgs mail and SMTP, messaging such as Twilio and Discord, Anthropic Claude, S3 compatible storage, PostNL shipping, Twinfield accounting, and more. Each integration has a page listing its blocks.
Where do I keep API keys for an integration in RUAL?
In a service provider where the service has one: the cluster holds the key and a block only names the provider, so it never sits on a pin or in a blueprint export.