← Back to catalog

Developer Tools

CircleCI

swirls add circleci
actionGETv1.0.0

get_me

Provides information about the signed in user.

Source
actionGETv1.0.0

get_project_username_project_build_num

Full details for a single build. The response includes all of the fields from the build summary. This is also the payload for the [notification webhooks](/docs/configuration/#notify), in which case this object is the value to a key named 'payload'.

Source
actionGETv1.0.0

get_project_username_project_build_num_tests

Provides test metadata for a build Note: [Learn how to set up your builds to collect test metadata](https://circleci.com/docs/test-metadata/)

Source
actionGETv1.0.0

get_projects

List of all the projects you're following on CircleCI, with build information organized by branch.

Source
actionGETv1.0.0

get_recent_builds

Build summary for each of the last 30 recent builds, ordered by build_num.

Source
actionPOSTv1.0.0

post_project_username_project_tree_branch

Triggers a new build, returns a summary of the build. Optional build parameters can be set using an experimental API. Note: For more about build parameters, read about [using parameterized builds](https://circleci.com/docs/parameterized-builds/)

Source
actionPOSTv1.0.0

post_user_heroku_key

Adds your Heroku API key to CircleCI, takes apikey as form param name.

Source
Beyond the catalog

Any provider, on request.

01

Request it

Tell us which provider you need, and we will ship it in the registry.

02

Generate it

Point swirls add at an OpenAPI or GraphQL spec. Typed actions for any API you hold credentials for, today.

acme · integrations
terminal
~/acme $swirls add linear
✓ 12 typed actions · scopes and schemas included
 
~/acme $swirls add https://api.acme.dev/openapi.json
◆ Fetched spec · 38 operations
✓ 6 typed actions · generated from spec