Contentstack Trigger

The Contentstack trigger lets you add Contentstack-specific trigger events, such as the creation/updating/publishing/unpublishing/deletion/deployment, etc., of workflows, entries, releases, global fields, assets, and/or content types.

Set up Contentstack

You will find the following trigger events for the Contentstack trigger:

• Workflow Trigger : Triggered when a workflow stage changes
• Entry Trigger : Triggered whenever you create/update/publish/unpublish/delete entries
• Release Trigger : Triggered when you deploy a release to an environment
• Global Field Trigger : Triggered when you create/update/delete global fields
• Asset Trigger : Triggered when you create/update/publish/unpublish/delete assets
• Content Type Trigger : Triggered when you create/update/delete content types

Note: After successfully configuring a trigger, if you re-configure any other trigger you will be prompted to revert to the previously configured trigger. You can revert back to the last trigger configurations by clicking the Revert Changes button.

Let’s look at each of them in detail.

Workflow Trigger

The Workflow Trigger event lets you trigger an automation when a workflow stage changes.

Let’s look at the steps to set up the trigger event.

1. Click Configure Trigger from the left navigation panel.
2. Within the Configure Trigger step, click the Contentstack connector.
   
3. Under the Choose Trigger tab, select Workflow Trigger.
   
4. In the Configure Trigger tab, click + Add New Account to add your Contentstack account.
   
5. A Permissions window opens. Provide the OAuth permissions for all the module-specific factors and click Authorize .
   

   Note: Contentstack offers support for branches in Automation Hub. You must authenticate and re-authorize your existing account by checking all the permissions to add your Contentstack account.

6. Select the Organization where you want to apply the Automation.
   
7. In the pop-up that appears, view the module-specific access rights provided to the app. Click Authorize to complete authorization.
   

   Note: You need to scroll down to view all the permissions.

8. Set the Account Name and click Save .
   
9. Select the trigger event from the dropdown, i.e., Workflow Stage Changed .
10. Select a Stack , Branch, Content Type , and Workflow from the Lookup dropdown.
    

    Note: By default, the main branch is selected (even if the Branch field is empty).

11. [Optional] Enable the Show optional fields toggle button to display the Workflow Stage field.
    
12. Click Proceed.
13. Click Test Trigger to execute and test the trigger that you configured.
    
14. If successful, you will see an output as follows. If it looks appropriate, click Save and Exit .
    

This sets your Workflow trigger.

Entry Trigger

The Entry Trigger event lets you trigger an automation when you create/update/publish/unpublish/delete entries.

Let’s look at the steps to set up the trigger event.

1. Under the Choose Trigger tab, select Entry Trigger .
   
2. In the Configure Trigger tab, click + Add New Account to add your Contentstack account.
   
3. A Permissions window opens. Provide the OAuth permissions for all the module-specific factors and click Authorize .
   

   Note: Contentstack offers support for branches in Automation Hub. You must authenticate and re-authorize your existing account by checking all the permissions to add your Contentstack account.

4. Select the Organization where you want to apply the Automation.
   
5. In the pop-up that appears, view the module-specific access rights provided to the app. Click Authorize to complete authorization.
   

   Note: You need to scroll down to view all the permissions.

6. Set the Account Name and click Save .
   
7. Select the trigger event from the dropdown, i.e, All . Select a Stack , and Branch from the Lookup dropdown.
   For Entries, you will find the following module-specific sub-events:
   • Entry Created: Triggers when you create a new entry
   • Entry Updated: Triggers when you update an entry
   • Entry Deleted: Triggers when you delete an entry
   • Entry Published: Triggers when you publish an entry
   • Entry Unpublished: Triggers when you unpublish an entry
   • Entry Publish Failed: Triggers when an entry publish activity fails
   • Entry Unpublish Failed: Triggers when an entry unpublish activity fails
   • ALL: Triggers when you perform any of the above activities on an entry
   

   Note: By default, the main branch is selected (even if the Branch field is empty).

8. [Optional] Enable the Show optional fields toggle button to display the Content Type and Environment fields.
9. Click Proceed .
   
10. Click Test Trigger to execute and test the trigger that you configured.
    

    Note: You can preview the latest data created in Contentstack without performing the trigger event. The latest data will be fetched and displayed to you after you test the trigger. You must click Retest to fetch the data you created in Contentstack.

    
11. If successful, you will see an output as follows. If it looks appropriate, click Save and Exit .
    

This sets your Entry trigger.

Release Trigger

The Release Trigger event lets you trigger an automation when you deploy a release in an environment.

Let’s look at the steps to set up the trigger event.

1. Under the Choose Trigger tab, select Release Trigger .
   
2. In the Configure Trigger tab, click + Add New Account to add your Contentstack account.
   
3. A Permissions window opens. Provide the OAuth permissions for all the module-specific factors and click Authorize .
   

   Note: Contentstack offers support for branches in Automation Hub. You must authenticate and re-authorize your existing account by checking all the permissions to add your Contentstack account.

4. Select the Organization where you want to apply the Automation.
   
5. In the pop-up that appears, view the module-specific access rights provided to the app. Click Authorize to complete authorization.
   

   Note: You need to scroll down to view all the permissions.

6. Set the Account Name and click Save .
   
7. Select the trigger event from the dropdown, i.e., Release Deployed and select a Stack , and Branch from the Lookup dropdown.
   

   Note: By default, the main branch is selected (even if the Branch field is empty).

8. [Optional] Enable the Show optional fields toggle button to display the Release , and Environment fields.
   
9. Click Proceed.
10. Click Test Trigger to execute and test the trigger that you configured.

    Note: You can preview the latest data created in Contentstack without performing the trigger event. The latest data will be fetched and displayed to you after you test the trigger. You must click Retest to fetch the data you created in Contentstack.

    
11. If successful, you will see an output as follows. If it looks appropriate, click Save and Exit .
    

This sets your Release trigger.

Global Field Trigger

The Global Field Trigger event lets you trigger an automation when you create/update/delete global fields.

Let’s look at the steps to set up the trigger event.

1. Under the Choose Trigger tab, select Global Field Trigger .
   
2. In the Configure Trigger tab, click + Add New Account to add your Contentstack account.
   
3. A Permissions window opens. Provide the OAuth permissions for all the module-specific factors and click Authorize .
   

   Note: Contentstack offers support for branches in Automation Hub. You must authenticate and re-authorize your existing account by checking all the permissions to add your Contentstack account.

4. Select the Organization where you want to apply the Automation.
   
5. In the pop-up that appears, view the module-specific access rights provided to the app. Click Authorize to complete authorization.
   

   Note: You need to scroll down to view all the permissions.

6. Set the Account Name and click Save.
   
7. Select the trigger event from the dropdown, i.e., Global Field Created and select a Stack, and Branch from the Lookup dropdown.
   For Global Field, you will find the following events:
   • Global Field Created: When you create a global field.
   • Global Field Updated: When you update a global field.
   • Global Field Deleted: When you delete a global field.
   • ALL: When you perform any of the above activities on a global field.
   

   Note: By default, the main branch is selected (even if the Branch field is empty).

8. [Optional] Enable the Show optional fields toggle button to display the specific Global Field.
   
9. Click Proceed.
10. Click Test Trigger to execute and test the trigger that you configured.

    Note: You can preview the latest data created in Contentstack without performing the trigger event. The latest data will be fetched and displayed to you after you test the trigger. You must click Retest to fetch the data you created in Contentstack.

    
11. If successful, you will see an output as follows. If it looks appropriate, click Save and Exit.
    

This sets your Global Field trigger.

Asset Trigger

The Asset Trigger event lets you trigger an automation when you create/update/publish/unpublish/delete assets.

Let’s look at the steps to set up the trigger event.

1. Under the Choose Trigger tab, select Asset Trigger .
   
2. In the Configure Trigger tab, click + Add New Account to add your Contentstack account.
   
3. A Permissions window opens. Provide the OAuth permissions for all the module-specific factors and click Authorize .
   

   Note: Contentstack offers support for branches in Automation Hub. You must authenticate and re-authorize your existing account by checking all the permissions to add your Contentstack account.

4. Select the Organization where you want to apply the Automation.
   
5. In the pop-up that appears, view the module-specific access rights provided to the app. Click Authorize to complete authorization.
   

   Note: You need to scroll down to view all the permissions.

6. Set the Account Name and click Save .
   
7. Select the trigger event from the dropdown, i.e., Asset Created and select a Stack, and Branch from the Lookup dropdown.
   For Asset Trigger, you will find the following events:
   • Asset Created: When you create a new asset in your stack.
   • Asset Updated: When you update an asset.
   • Asset Deleted: When you delete an asset.
   • Asset Published: When you publish your assets to a publishing environment.
   • Asset Publish Failed: When asset publishing fails due to error.
   • Asset Unpublished: When you unpublish or remove your assets from a publishing environment.
   • Asset Unpublish Failed: When the asset unpublishing activity fails.
   • ALL: When you perform any of the above activities on an asset.
   

   Note: By default, the main branch is selected (even if the Branch field is empty).

8. Click Proceed .
9. Click Test Trigger to execute and test the trigger that you configured.
   
10. If successful, you will see an output as follows. If it looks appropriate, click Save and Exit .
    

This sets your Asset Trigger.

Content Type Trigger

The Content Type Trigger event lets you trigger an automation when you create/update/delete content types.

Let’s look at the steps to set up the trigger event.

1. Under the Choose Trigger tab, select Content Type Trigger .
   
2. In the Configure Trigger tab, click + Add New Account to add your Contentstack account.
   
3. A Permissions window opens. Provide the OAuth permissions for all the module-specific factors and click Authorize .
   

   Note: Contentstack offers support for branches in Automation Hub. You must authenticate and re-authorize your existing account by checking all the permissions to add your Contentstack account.

4. Select the Organization where you want to apply the Automation.
   
5. In the pop-up that appears, view the module-specific access rights provided to the app. Click Authorize to complete authorization.
   

   Note: You need to scroll down to view all the permissions.

6. Set the Account Name and click Save .
   
7. Select the trigger event from the dropdown, i.e., Content Type Created and select a Stack, and Branch from the Lookup dropdown
   For Content Type Trigger, you will find the following events:
   • Content Type Created: When you create a new content type.
   • Content Type Updated: When you update a content type.
   • Content Type Deleted: When you delete a content type.
   • ALL: When you perform any of the above activities on a content type.
   

   Note: By default, the main branch is selected (even if the Branch field is empty).

8. [Optional] Enable the Show optional fields toggle button to display the specific Content Type .
   
9. Click Proceed .
10. Click Test Trigger to execute and test the trigger that you configured.

    Note: You can preview the latest data created in Contentstack without performing the trigger event. The latest data will be fetched and displayed to you after you test the trigger. You must click Retest to fetch the data you created in Contentstack.

    
11. If successful, you will see an output as follows. If it looks appropriate, click Save and Exit .
    

This sets your Content Type trigger.