Every Integration APES Connects to Today
A workflow platform that can only move data around inside itself is really just a filing cabinet with extra steps. The moment a business actually tries to run its operations on one, it needs that platform to reach outward, into the identity provider staff already log into, the payment system that actually moves money, the document tool that gets a contract signed, and the chat app a team already lives in every day.
This post is a tour of what APES already connects to today, not a roadmap of what is planned. Every integration named here exists as real, working code in the product right now. A few of them get a full post of their own later in this series, with live demonstrations on the actual product. This one is the map of everything else.
Signing In With an Identity Your Team Already Has
Most companies do not want to manage yet another separate password for yet another system. APES supports signing in through Google, through Apple, and through Microsoft Entra ID, which is Microsoft's identity platform used by a large share of businesses already running on Microsoft 365. A staff member can sign into their APES workspace the same way they sign into everything else their company already uses, and a departing employee loses access the moment their identity provider account is disabled, without anyone needing to remember to remove them from a second, separate system.
Bringing AI Into a Workflow, Not Just a Chat Window
APES includes a direct connection to Claude, Anthropic's AI model, as a step inside a workflow itself. Rather than a person copying data into a separate chat window and pasting an answer back, a workflow can ask Claude a question directly, using the run's own data, and read the answer straight back into the next step. This has already been covered in detail earlier in this series, and a dedicated post later on will walk through it live, with real screenshots of a working example.
Getting Paid and Moving Money
Payments are one of the areas where a workflow platform genuinely earns its place, because so much of the manual work in a business happens around money actually changing hands. APES connects to Airwallex, a global payments and financial operations platform, covering account management, payouts, foreign exchange, card issuing, and batch payment runs, all of which can sit as steps inside a workflow rather than a separate manual process someone repeats every time.
For businesses operating in Malaysia specifically, APES also connects to Curlec and to SenangPay, two payment gateways used widely in that market. A workflow can check the status of an order's payment directly, rather than someone logging into a separate dashboard to look it up by hand every time a customer asks.
Verifying Who Someone Actually Is
Some businesses, particularly anything involving lending, consignment stock, or other regulated activity, need to know more about a person or a company than a name on a form. APES connects to CTOS, a well known credit reporting and identity verification service in Malaysia, covering both electronic know your customer checks and full credit reports. A workflow can run this check automatically as part of onboarding a new customer or approving a larger transaction, rather than someone manually requesting a report and waiting to attach it to a file later.
Getting a Document Actually Signed
A contract, an approval, or an order confirmation often has to leave the building entirely to get signed, and then someone has to remember to bring it back into the system afterward. APES connects to DocuSeal, an electronic signature service, so a document can be sent out for signature, tracked while it is out, and brought back in automatically once it is signed, as steps inside the same workflow that generated it in the first place, without anyone having to manually watch an inbox for it to come back.
Reaching a Team Where It Already Works
Notifications only help if people actually see them. Alongside the in app notifications described earlier in this series, APES connects to Lark and to DingTalk, two workplace communication platforms widely used across Asia, so a workflow can reach someone through the chat tool their team already lives in every day, rather than asking them to check a separate system on top of everything else.
Sending Mail Like Mail
For everything else, APES includes a direct email sending connection, so a workflow can send a real email from a step, whether that is a confirmation, a reminder, or a formal notice that needs to exist as an email specifically, rather than only as an in app message.
Configured Once, Trusted Everywhere After
It is worth being clear about how these integrations are actually set up, because it matters for the same reasons covered in the security post earlier in this series. Each of these connects through a governed connection held by the workspace itself, not through a credential pasted into one particular workflow. Once someone with the right authority sets a connection up, any workflow that is allowed to use it can, without anyone needing to hand a password or an API key around between different people building different processes. If a connection is ever revoked, every workflow using it stops being able to reach that system immediately, in one place, rather than requiring someone to hunt down every workflow that happened to have a copy of the old credential.
What This Actually Means for a Business
None of these integrations exist because they look good on a list. Each one removes a specific piece of manual work that a business is probably still doing by hand today, checking a payment status, re typing a credit report into a form, watching an inbox for a signed document to come back, or logging into a second chat app to tell someone something they should already know from their own workflow. Put together, they are what turns APES from a tool that organises a business's own internal data into one that can actually run a process from end to end, including the parts that happen outside the business itself.
The next few posts in this series each take one of these integrations and show it running for real inside the product, starting with the Claude AI step already introduced earlier in this series.