Sync assets from multiple repositories

Consolidate element templates spread across several repositories into a single collection repository before syncing to the Hub catalog.

When to use this guide

The catalog syncs from a single repository. Depending on your setup, you may or may not need this guide:

• ❌ If your element templates already live together in one repository, sync from it directly. You do not need this guide.
• ✅ If your element templates are spread across several repositories, you need to consolidate them before syncing. This guide shows you how.

Consolidate templates into a collection repository

Camunda recommends using a CI/CD job in each source repository that copies its element templates and READMEs into a dedicated collection repository whenever a new version is created. For example:

# Example: GitHub Actions workflow in a source repository
name: Push templates to collection repo

on:
  push:
    branches: [main]

jobs:
  push-to-collection:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout source repository
        uses: actions/checkout@v4

      - name: Push element templates to collection repo
        run: |
          git clone https://x-access-token:${{ secrets.COLLECTION_REPO_TOKEN }}@github.com/your-org/catalog-collection.git
          cp -r element-templates/payment-connector catalog-collection/payment-connector
          cd catalog-collection
          git add .
          git commit -m "Update payment-connector templates"
          git push

The collection repository then syncs to Camunda Hub.

Next steps

• Get started with the catalog — set up the repository and CI/CD pipeline.
• Manage the asset lifecycle — unpublish and delete catalog assets.