Integration Settings
Customize and manage your integration after setup.
Last updated
Customize and manage your integration after setup.
Last updated
On the Integrations page, you can easily view and search through all your integrations. You can see details about your integrations including the last and upcoming runs, as well as the status of the most recent run. Additionally, you can use the command palette to run or delete multiple integrations at once.
Deleting an integration from the workspace will remove all associated resources.
If you click into an integration, the following options become available.
After selecting an integration, you'll find the Enabled toggle in the top right corner. By default, all integrations are enabled. If toggled off, the integration is paused, meaning it will not run automatically based on the schedule set.
In the top right corner, you'll also see the Run Sync button. This action triggers a manual sync. Clicking this button allows you to choose whether the sync should Pull or Push metadata.
This is the first page you’ll see when you navigate to an integration. It provides a detailed history of past syncs, allowing you to review each sync's stages, the number of resources pulled, and any errors that may have occurred.
To automate your syncs, use this page to set the run frequency with a Cron Expression. You can learn more about Cron Expressions . If you don’t specify a schedule, the default is 0 0 * * *
, which runs the sync daily at midnight UTC.
If applicable to the integration, use this page to select which Groups or Schemas you want to sync. Click the Refresh button to check for any new Groups or Schemas available for import. By default, all Groups and Schemas will be selected and included in the sync. If you'd like to change this default behaviour, navigate to the integrations page and change the schemas imported to Seda.
When setting up integrations in Seda, you may notice that some settings pages or references mention "Secoda" instead of "Seda." This is expected and not a cause for alarm. Since Seda shares some architecture with Secoda's platform and is maintained by the same company, some integration components and backend systems use the same framework. These references to Secoda simply reflect the shared infrastructure between the two platforms and do not impact the functionality or security of your Seda implementation