Custom API Action (CAPIA) cards
Custom API Action cards allow a connector to scale in front of development efforts. They provide users the ability to hit any endpoint for an API, even if you haven't built out a specific action. For OAuth, this is dependent on the enabled scopes. CAPIAs don't provide the added usability of a standard Workflows card, and much of the complexity that connectors abstract is left to the user to define.
A CAPIA-only connector includes three or four flows, depending on the service's auth type and endpoints:
-
httpHelper
-
Custom API Action
-
_authping
-
_revoke (token based services only)