Skip to content

EP Composio

EP Composio brings a connector catalogue to EP Flows. EP Flows is the engine: trigger, conditions, chained actions and a run ledger. Composio supplies the apps (Gmail, Slack, Notion, HubSpot, Google Sheets, GitHub and around a thousand more) and the sign-in to reach them.

Your site never stores a password or access token for those apps. People sign in on a page Composio hosts, Composio keeps the connection fresh, and your site only learns which connected account to use.

Published by ElmsPark Studio.

  • PageMotor 0.11.5 or later
  • EP Flows 0.3.0 or later, active. If EP Flows is not active, EP Composio does not appear anywhere: no settings screen and no message. Activate EP Flows first. If EP Flows is active but older than 0.3.0, the settings screen appears and tells you so.
  • A Composio account and a project API key.
  • EP Suite base class (bundled)
  1. Paste your Composio project API key into Composio → Composio account.
  2. Set a default Composio user id if you want something more meaningful than pagemotor-site.
  3. To start flows from events in other apps, create a webhook subscription in Composio pointing at the trigger receiver URL shown on the settings screen, then paste its whsec_… secret into Trigger webhook secret.

Leave Verify incoming trigger events on standard. The other setting is only for testing a brand-new connection, and it switches itself back after a day.

Add a composio action to any flow:

{
"type": "composio",
"config": {
"tool": "GMAIL_SEND_EMAIL",
"arguments": {
"recipient_email": "{{trigger.email}}",
"subject": "Thanks for getting in touch",
"body": "Hi {{trigger.name}}, we have your enquiry."
}
}
}

Find the pieces with your site’s MCP tools rather than guessing:

ToolWhat it tells you
composio_toolkitsWhich apps exist
composio_toolsThe actions inside one app
composio_tool_schemaThe exact argument names for one action
composio_executeRuns an action once, for real, before you wire it into a flow

arguments is fully templated, so {{trigger.x}} and {{steps.N.data.y}} both work inside it.

A composio action returns the app’s response as its step data, so the next step can use it:

"actions": [
{ "type": "composio",
"config": { "tool": "NOTION_CREATE_PAGE",
"arguments": { "title": "{{trigger.name}}" } },
"on_error": "stop" },
{ "type": "composio",
"config": { "tool": "SLACK_SEND_MESSAGE",
"arguments": { "channel": "#sales",
"text": "New page: {{steps.0.data.url}}" } } }
]

Set on_error: "stop" on any step a later step depends on. Without it, a failed step does not halt the chain, and the next step would post an empty value.

  1. composio_auth_configs: get the auth_config_id for the app.
  2. composio_connect_link: create a hosted sign-in link.
  3. Send that link to whoever owns the account. They sign in on Composio.
  4. composio_accounts: confirm the account shows ACTIVE and note its id.

Put that id in a flow action’s connected_account_id when your site has more than one account for the same app. Leave it out to use the project default.

Two steps, and both are needed.

Turn the trigger on in Composio, so events start arriving:

composio_trigger_enable
trigger_slug: GMAIL_NEW_GMAIL_MESSAGE
connected_account_id: ca_...

Write a flow that listens for it:

{
"name": "Log new Gmail",
"trigger": { "type": "composio",
"config": { "trigger_slug": "GMAIL_NEW_GMAIL_MESSAGE" } },
"actions": [ { "type": "log",
"config": { "message": "mail from {{trigger.data.sender}}" } } ]
}

Composio sends every event in the project to the one receiver address. EP Composio checks each event once, then runs every flow whose trigger_slug matches (and connected_account_id, if the flow sets one). The whole event is available as {{trigger.*}}.

The settings screen lists recent trigger deliveries: every event Composio sent, whether it was accepted and whether it started a flow.

What you seeWhat it means
No rows at allComposio is not reaching your site. Check the webhook subscription address.
Verified: noThe event was refused. Usually the wrong whsec_… secret, or your server’s clock is more than five minutes out.
Verified: yes, Flows fired: 0The event arrived, but no flow matched. Check the trigger_slug spelling and that the flow is enabled.
A flow fired with the wrong resultRead the run ledger on the EP Flows screen.

composio_status gives the same information over MCP, plus whether your API key works.

Composio bills per action. Every composio step in a flow run counts as one, as does each composio_execute. A flow that fires often with several Composio steps adds up quickly, so check it against your Composio plan before switching a busy trigger on.

  • No admin screen for building flows: you build them over MCP or the API, as with EP Flows.
  • No polling fallback. If Composio cannot reach your site, those events are not queued.
  • The app catalogue is fetched on first use, so the first composio_tools call for an app takes a moment longer.
  1. Install and activate EP Flows first.
  2. ep-composio.zip comes with an EP Suite licence, supplied directly by ElmsPark (see EP Suite plugins); after install it updates through your site’s Updates screen.
  3. Upload via Plugins → Manage Plugins. Activate.
  4. Open Plugin Settings → EP Composio and follow the setup steps above.
  • Changing this plugin’s settings over the API now needs an admin token. Producer tokens and AI apps connected through a producer account can still read the settings. Saving from the Admin screen works exactly as before.
  • Now requires PageMotor 0.11.5, the current release, while PageMotor is in beta.
  • First release on the ElmsPark update channel: after this, updates arrive through your site’s Updates screen.