Action Collections | Chipp Docs

Action Collections let you bundle related custom actions together and reuse them across your apps or share them with your workspace. Instead of recreating the same API integrations for each app, build them once and add them everywhere.

What Are Action Collections?

A collection is a saved copy of one or more custom actions from one of your apps:

Feature	Description
Bundled actions	Group related API integrations together
Shareable	Keep it private or share it with your workspace
Configurable	Each app sets its own variable values (API keys, base URLs)
Versioned	Re-publish to update the collection; the version number goes up

Creating a Collection

Create Custom Actions

First, create the custom actions you want to bundle in your app’s Build > Connect > Custom APIs section.

Publish as Collection

Below your custom actions you’ll find the Action collections card. Once your app has at least one custom action, click Publish as collection.

Configure your collection:

Name: A descriptive name (e.g., “Stripe Payments”)
Description: What the collection does and what it needs
Actions: Select which actions to include (up to 50)

Choose Who Can Use It

Scope	Who Can Access
Private	Only you, in any app you can edit
Workspace	Everyone in the app’s workspace, in apps in that workspace

You can change this later from Your collections in the same card. To share with a workspace, you need edit access to custom actions in that workspace.

Adding a Collection to Your App

Browse Available Collections

In the Action collections card, click Browse collections to see what you can add:

Your collections: Collections you’ve published
Shared with your workspace: Collections your teammates shared with this app’s workspace
From Chipp: Collections reviewed and approved by Chipp

A workspace collection only appears for members of that workspace, and you can only add it to apps in that workspace.

Add It

Find the collection you want
Click Add to app
Fill in any variables the collection needs (see below)

The actions are copied into your app as regular custom actions. Adding the same collection twice does nothing the second time. You need edit access to custom actions on the app.

Variables and Configuration

Collections use Application Variables for values that differ between apps.

What Are Variables?

Variables are placeholders that each app fills in for itself:

plaintext

API URL: https://api.example.com/v1
API Key: {{var.API_KEY}}       <- Variable

What Travels With a Collection

When you publish, the collection records each variable’s name, label, and type. It never records the value. Your API keys stay in your app.

When someone adds the collection, Chipp creates any missing variables in their app with an empty value. The success message lists the variables to fill in.

Setting Variable Values

Open Build > Connect > Custom APIs
Open the Variables section
Enter a value for each variable the collection needs

Secret variables are encrypted and hidden in the UI.

Managing Collections

View Your Collections

The Action collections card shows:

Added to this app: collections whose actions this app holds
Your collections: collections you’ve published, with their sharing setting

Update a Collection

Change the custom actions in your app
In Your collections, click Re-publish
Pick the actions the collection should hold

Re-publishing replaces the collection’s actions and bumps its version. Apps that already added the collection keep their current copies. To pick up the new version, remove the collection from the app and add it again.

Remove a Collection From an App

Find the collection under Added to this app
Click Remove collection

This removes the collection’s actions from that app only. It does not delete the collection or touch any other app.

Delete a Collection

Only the person who published a collection can rename, re-publish, share, or delete it. Click Delete in Your collections. Apps that already added it keep those actions as ordinary custom actions.

Best Practices

Organizing Collections

Create focused collections around a single integration or use case:

Good:

“Stripe Payments” - Charge, refund, subscription actions
“HubSpot CRM” - Contact, deal, company actions
“Email Tools” - Send, template, tracking actions

Avoid:

“All My Actions” - Too broad, hard to maintain
“Misc Utilities” - No clear purpose

Variable Naming

Use clear, consistent variable names:

plaintext

Good:
- STRIPE_API_KEY
- HUBSPOT_ACCESS_TOKEN
- BASE_URL

Avoid:
- key
- token1
- url

Put credentials in variables, not in header values. A value typed directly into a header is part of the action, so it is copied with the collection.

Documentation

Add descriptions to your collections and actions:

What does each action do?
What variables are required?
Any prerequisites or setup needed?

Troubleshooting

”Variable is empty” when an action runs

The collection added a variable but no value is set yet:

Open the Variables section under Custom APIs
Enter the missing values

”Action not working after adding”

Check variable values are correct
Verify API credentials are valid
Test the action with Test Request in the action editor

”Can’t see workspace collections”

Check you are in the right workspace
Check the collection’s sharing is set to Workspace
Ask the person who published it to confirm it was published from an app in this workspace

”Can’t add a workspace collection to my app”

A workspace collection can only be added to apps in its own workspace. Ask the publisher to share it from your workspace, or publish your own copy.

Next Steps

With action collections:

Learn about Custom Actions to build your own integrations
Explore Pro Actions for pre-built integrations
See Parameter Configuration for advanced configuration