Exhibit & Collection ManagementPurpose
1.2. Automate the notification process to alert staff, curators, and interested visitors when new items are added, updated, or become temporarily unavailable, supporting operational efficiency, visitor engagement, and regulatory compliance.
Trigger Conditions
2.2. Scheduled synchronization intervals (e.g., daily, hourly).
2.3. API push notifications from artifact acquisition or lending management systems.
2.4. Manual trigger by museum administrator for bulk catalog updates.
Platform Variants
• Feature/Setting: Trigger—SharePoint List Item Modified; Action—Teams notification; configure SharePoint and Teams connectors.
3.2. Zapier
• Feature/Setting: New Record in Airtable (Trigger), Send Email via Gmail (Action); configure with museum’s Airtable DB and Gmail accounts.
3.3. Make (Integromat)
• Feature/Setting: Watch Records in Google Sheets, Webhooks module to trigger Slack alerts; endpoint setup for artifacts sheet.
3.4. Salesforce Platform Events
• Feature/Setting: Create Platform Event; Process Builder to automate notifications based on catalog changes.
3.5. Smartsheet Automation
• Feature/Setting: Change in row triggers update notification to assigned users; setup using Smartsheet’s automation rules.
3.6. Trello API
• Feature/Setting: Card Created/Updated trigger via Power-Up; action—Slack message through Trello/Slack integration.
3.7. Asana Rules
• Feature/Setting: Task added to project (catalog entry), trigger rule to send email using the built-in mail integrator.
3.8. Slack API
• Feature/Setting: Events API listens for update events; automated bot posts announcements to #exhibit-alerts channel.
3.9. SendGrid API
• Feature/Setting: REST API POST to /mail/send when catalog change is detected; use dynamic templates for notifications.
3.10. Twilio Programmable SMS
• Feature/Setting: Send text notification via REST API on new artifact; secure with API credentials.
3.11. HubSpot Workflows
• Feature/Setting: Trigger on custom field change (e.g., "collection update"); send automated emails to subscription list.
3.12. Notion API
• Feature/Setting: Page updated trigger; automatedly push updated catalog details to external dashboard via integration.
3.13. Monday.com Automation
• Feature/Setting: Item updated in board; automate notification or webhook to third-party systems.
3.14. Pipedream
• Feature/Setting: Event source watches for API catalog updates; action sends notifications automatically to multiple services.
3.15. Google Workspace Apps Script
• Feature/Setting: Script runs on Google Sheets change, triggers automated emailing and adds log entry to Drive.
3.16. API Webhooks (Generic)
• Feature/Setting: Send HTTP request from museum catalog backend on data change; target endpoint for notifications.
3.17. IFTTT
• Feature/Setting: Applet triggers on Google Sheets or Feed update, automates push notification via mobile.
3.18. Workato
• Feature/Setting: Catalog system event triggers recipe, automatedly syncs updates to external CRMs or messaging apps.
3.19. Freshdesk Automator
• Feature/Setting: Ticket creation for each update, automates task assignment for review and communication.
3.20. Shopify API
• Feature/Setting: Product/Inventory update webhook, automates notification to exhibit commerce team via webhooks.
Benefits
4.2. Speeds up staff awareness of critical exhibit changes, enhancing exhibit management automation.
4.3. Increases visitor engagement through timely, automated notifications for new or changed exhibits.
4.4. Supports regulatory/insurance compliance with automated catalog audit trails.
4.5. Frees resources for curatorial tasks by reducing low-value, repetitive updating and messaging activities.