.png)
Showpad Integration Guide
Connect Showpad’s OAuth 2.0-secured REST APIs with enterprise applications through scheduled synchronization, content workflows, and controlled API orchestration.
Showpad integration options at a glance
Showpad’s primary integration mechanism is its REST API, authenticated with OAuth 2.0 and used to access resources such as Users, Content, Collections, Tags, Portals, and content metadata. Showpad may provide webhook-style notifications for selected integration scenarios, but event coverage should be confirmed for each tenant, object, and API version. Content-related file operations are available in the API surface, although upload, download, rendition, and size-limit behavior require verification. Martini can call Showpad APIs, manage secrets, paginate and checkpoint synchronization, transform JSON and content metadata, expose intermediary REST APIs, and run scheduled workflows when callbacks are unavailable.
| Integration point | Supported by Showpad? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST APIs | Yes | Showpad REST APIs provide programmatic access to Users, Content, Collections, Tags, Portals, and content metadata. They are the recommended foundation for new integrations. | Martini can consume the REST API from workflows, manage authenticated requests, transform JSON responses, expose intermediary APIs, and coordinate downstream writes. |
| Webhooks and outbound callbacks | Limited | Showpad may support event or notification-oriented callbacks for selected product and integration scenarios, but universal coverage across objects and events is not confirmed. | Martini can expose an endpoint to receive a confirmed callback, validate and deduplicate it, retrieve the authoritative Showpad object, and process it asynchronously. |
| File and attachment APIs | Limited | Showpad is centered on content assets and exposes content-related operations. Exact upload, download, rendition, temporary URL, and file-size behavior must be verified for the API version and tenant. | Martini can orchestrate binary or URL-based transfers, preserve content metadata, apply duplicate checks, and route large-file failures for recovery. |
| Authentication | Yes | Showpad API access uses OAuth 2.0 with application credentials, bearer tokens, and tenant-specific authorization details. Exact grants, scopes, and token lifetime require confirmation. | Martini can store credentials in environment-specific secrets, obtain and refresh tokens as required, apply bearer authentication, and handle unauthorized responses. |
| Scheduled synchronization | Yes | Scheduled polling is an appropriate fallback when a required Showpad event is unavailable or only partially supported. REST pagination, filtering, and checkpoints support incremental processing where available. | Martini can trigger workflows on a schedule, persist checkpoints, page through results, apply bounded retries, and write synchronized data to enterprise targets. |
| Bulk and asynchronous APIs | Not confirmed | A dedicated general-purpose bulk or asynchronous API was not confirmed. High-volume processing should use documented REST pagination and filtering unless a tenant-specific facility is verified. | Martini can coordinate paginated batches, checkpoint progress, throttle requests, and retry transient failures without assuming a bulk endpoint exists. |
| Database and analytics access | No | Direct database access was not confirmed and should not be used. Usage or analytics data should come from documented API resources or supported exports where available. | Martini can consume supported API or file exports and transform them for reporting systems, but it does not require or assume direct access to Showpad’s internal database. |
| SDKs | Not confirmed | An official Showpad SDK was not confirmed for the selected API version and language. Direct HTTP API consumption is the safer integration baseline. | Martini can call Showpad HTTP APIs directly and use custom JVM-compatible logic only when orchestration or transformation needs exceed built-in workflow capabilities. |
How Showpad exposes data and business events
Showpad REST APIs
Showpad’s documented REST APIs are the primary mechanism for accessing platform resources, including Users and content-related objects. Endpoint fields, operations, pagination, filtering, and API-version behavior should be confirmed against the tenant documentation.
Martini implementation pattern
Martini implementation pattern: a workflow authenticates with OAuth 2.0, calls the relevant Showpad endpoint, follows pagination, transforms the JSON response, applies business rules, and writes the result to an enterprise target or returns it through a Martini API.
Implementation sequence
Showpad webhook-style callbacks
Showpad may provide event or notification-oriented callbacks for selected integration scenarios, but broad coverage across Users, Content, Collections, Tags, and Portals is not confirmed. Required events, payloads, signatures, and retry behavior must be verified.
Martini implementation pattern
Martini implementation pattern: expose a controlled REST endpoint for the confirmed callback, acknowledge quickly, validate the event, deduplicate it, retrieve the authoritative Showpad object, and process the change in a separate workflow.
Implementation sequence
Showpad content and file operations
Showpad’s platform and API surface are centered on content assets. The exact binary transfer, upload, download, rendition, temporary URL, versioning, and file-size behavior varies by API version and tenant and must be verified.
Martini implementation pattern
Martini implementation pattern: retrieve or submit the content representation supported by Showpad, process metadata separately from the binary asset, apply file and duplicate checks, and route incomplete or failed transfers for recovery.
Implementation sequence
Scheduled Showpad synchronization
Scheduled polling is the recommended fallback when the required Showpad event is unavailable or only partially supported. Workflows should use documented filters, modification fields, pagination, and checkpoints rather than assuming a bulk API exists.
Martini implementation pattern
Martini implementation pattern: a scheduler starts a workflow, the workflow reads the last successful checkpoint, retrieves changed pages from Showpad, processes records idempotently, and advances the checkpoint only after successful handling.
Implementation sequence
Common Showpad integration patterns
Pattern 1: Synchronize Showpad users and content context with a CRM
When to use this pattern
Use this pattern when sales teams need Showpad identities, content groupings, or metadata available in Salesforce or Microsoft Dynamics 365. It supports scheduled synchronization and can use a confirmed callback for selected events.
Integration direction
Example Mapping
| Showpad Field | Canonical Field | Target Field |
|---|---|---|
| User.id | externalUserId | Showpad_User_Id__c |
| User.status | userStatus | Status |
| Content.id | contentId | Showpad_Content_Id__c |
| Content.metadata.region | contentRegion | Region__c |
Martini implementation pattern
Martini retrieves changed Users, Content, and Collections through the Showpad REST API, follows pagination, maps source identifiers and metadata into CRM objects, and applies create, update, or deactivation rules. Stable external keys make processing idempotent; transient API failures are retried and invalid records are routed for review.
Martini capabilities used
- workflows
- API consumption
- OAuth 2.0 configuration
- data mapping
- business rules
- scheduled triggers
- error handling
Pattern 2: Publish governed content to Showpad
When to use this pattern
Use this pattern when an enterprise content or governance process approves assets before they are created or updated in Showpad. It is useful for enforcing title, owner, category, region, expiration, and duplicate rules before publication.
Integration direction
Example Mapping
| Showpad Field | Canonical Field | Target Field |
|---|---|---|
| sourceAsset.externalId | sourceContentId | Content.externalId |
| sourceAsset.title | contentTitle | Content.title |
| sourceAsset.owner | contentOwner | Content.owner |
| sourceAsset.expirationDate | contentExpiration | Content.metadata.expirationDate |
Martini implementation pattern
A Martini API or workflow receives approved content metadata and, where supported, the binary asset. It validates required fields, checks the source identifier for an existing Showpad Content object, calls the appropriate Showpad REST operation, and records the resulting identifier and version. Validation errors stop publication while transient failures use bounded retries.
Martini capabilities used
- API exposure
- workflows
- file handling
- data mapping
- validation
- business rules
- error handling
Pattern 3: Distribute approved Showpad content to collaboration channels
When to use this pattern
Use this pattern when approved Showpad Content must be shared with internal teams through Microsoft Teams, Slack, or an email-based process. Business rules can restrict distribution by audience, region, product, or expiration date.
Integration direction
Example Mapping
| Showpad Field | Canonical Field | Target Field |
|---|---|---|
| Content.title | assetTitle | message.title |
| Content.url | assetLink | message.link |
| Content.metadata.region | audienceRegion | message.region |
| Content.metadata.expirationDate | validUntil | message.expiration |
Martini implementation pattern
Martini retrieves eligible Content and metadata, evaluates governance rules, and transforms the result into the destination platform’s message or supported file format. The workflow prefers controlled Showpad links when appropriate, prevents duplicate notifications using the Showpad identifier, and retries destination throttling or transient failures.
Martini capabilities used
- workflows
- API consumption
- data mapping
- business rules
- scheduled triggers
- error handling
Pattern 4: Export Showpad content and user audit data
When to use this pattern
Use this pattern for governance, reporting, archival, or operational review of Showpad Users, Content, Collections, Tags, Portals, and metadata. It is appropriate when no suitable event or bulk API is confirmed.
Integration direction
Example Mapping
| Showpad Field | Canonical Field | Target Field |
|---|---|---|
| Content.id | sourceObjectId | showpad_content.source_id |
| Content.updatedAt | sourceUpdatedAt | showpad_content.updated_at |
| Content.metadata.category | contentCategory | showpad_content.category |
| User.status | userStatus | showpad_user.status |
Martini implementation pattern
A scheduled Martini workflow reads the last checkpoint, retrieves paginated Showpad resources, converts JSON into database rows or CSV and Excel output, and commits progress only after successful writes. It reports failed pages, handles rate limits with backoff, and uses stable identifiers to avoid duplicate exports.
Martini capabilities used
- scheduler triggers
- workflows
- API consumption
- pagination orchestration
- JSON transformation
- database or file output
- checkpointing
- error handling
Applications commonly integrated with Showpad
Showpad can be integrated with adjacent sales, collaboration, identity, and enterprise workflow applications through standards-based API orchestration. The exact native capabilities of each product pairing should be verified separately; Martini can coordinate the confirmed APIs, files, callbacks, and business rules across the systems.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| Salesforce | Align Showpad Users and content metadata with sales processes, and make approved content links available in CRM workflows. | Showpad → Martini → Salesforce | A scheduled or event-triggered Martini workflow retrieves changed Showpad Users, Content, or Collections, maps stable identifiers and metadata to Salesforce objects, applies create-or-update rules, and retries transient failures. |
| Microsoft Dynamics 365 | Synchronize seller identities and make approved Showpad content available to Dynamics-based sales teams. | Showpad → Martini → Microsoft Dynamics 365 | Martini consumes Showpad REST responses, transforms user and content metadata into Dynamics 365 payloads, validates required fields, and records checkpoints for incremental synchronization. |
| HubSpot | Connect approved sales and marketing content with HubSpot contacts, companies, deals, and related sales processes. | Showpad → Martini → HubSpot | A workflow retrieves eligible Showpad Content and metadata, applies audience and expiration rules, and sends controlled content links or activity data to HubSpot while preventing duplicates. |
| Microsoft Teams | Distribute approved Showpad content links or notifications to internal sales and collaboration channels. | Showpad → Martini → Microsoft Teams | Martini polls or receives confirmed Showpad notifications, checks region, audience, product, and expiration rules, then transforms eligible content into Teams messages or supported file representations. |
| Slack | Share approved Showpad content links and notifications with sales or marketing channels. | Showpad → Martini → Slack | A Martini workflow retrieves content metadata, filters it according to governance rules, and posts a formatted Slack notification with a controlled Showpad link, using bounded retries for transient failures. |
| Outlook | Support email-based sales workflows by making approved Showpad content available for standardized sharing. | Showpad → Martini → Outlook | Martini retrieves approved content and metadata, applies recipient and expiration rules, and formats a link or supported content representation for an Outlook-based process without exposing Showpad credentials. |
| Workday | Align organizational and user lifecycle information with Showpad user provisioning and access-management processes. | Workday → Martini → Showpad | A scheduled workflow reads relevant Workday worker changes, maps identity and status fields to Showpad Users where supported, and routes authorization or validation failures for review. |
| ServiceNow | Route Showpad access, content governance, or support requests through enterprise workflow processes. | ServiceNow → Martini → Showpad | Martini receives or polls ServiceNow requests, validates the requested Showpad action, calls the applicable Showpad REST endpoint, and updates the request with the result and operational details. |
How to build a Showpad integration in Martini
Objective
Establish a tenant-specific Showpad API connection using OAuth 2.0 and environment-specific configuration.
Instructions in Martini
- Configure the Showpad tenant endpoint and authorization details
- Store client credentials and token material in Martini secrets
- Confirm required grants, scopes, and administrator approval
- Prevent bearer tokens and authorization responses from entering logs
Objective
Select a confirmed Showpad callback for near-real-time processing or use scheduled polling for reliable incremental synchronization.
Instructions in Martini
- Verify the required event and callback behavior with Showpad
- Expose a Martini REST endpoint only when a callback is confirmed
- Otherwise configure a scheduler trigger
- Define the synchronization checkpoint and polling window
Objective
Call the relevant Showpad REST resources and retrieve authoritative objects, metadata, and supported file representations.
Instructions in Martini
- Invoke the Users, Content, Collections, Tags, Portals, or metadata endpoint
- Follow endpoint-specific pagination and filtering rules
- Retrieve the authoritative object after a notification when necessary
- Handle binary content and temporary URLs according to the verified API behavior
Objective
Coordinate API calls, pagination, enrichment, routing, and target writes in a maintainable Martini workflow.
Instructions in Martini
- Separate notification receipt from long-running processing
- Use reusable workflow logic for authentication and pagination
- Apply conditional routing for object type, audience, region, or status
- Persist checkpoints only after successful processing
Objective
Convert Showpad JSON, metadata, and file information into the target application or export format.
Instructions in Martini
- Map stable Showpad identifiers to target external keys
- Transform dates, statuses, tags, collections, and custom metadata
- Keep binary content separate from descriptive metadata
- Validate required fields before downstream writes
Objective
Enforce publication, distribution, deactivation, duplicate, and data-quality rules before committing changes.
Instructions in Martini
- Reject incomplete content or user payloads
- Check expiration, region, audience, owner, and classification fields
- Use create-or-update behavior with explicit duplicate prevention
- Route exceptions for manual review without advancing the checkpoint
Common Showpad data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Users | Synchronize Showpad identities, status, and access-related information with enterprise user or sales systems. | Salesforce, Microsoft Dynamics 365, Workday, identity and provisioning workflows | Martini retrieves Users through REST endpoints, maps stable identifiers and status fields, applies activation or deactivation rules, and checkpoints processed changes. |
| Content | Synchronize sales and marketing assets, links, versions, ownership, classification, and approval-related metadata. | Salesforce, Microsoft Teams, Slack, Outlook, content governance platforms | Martini separates binary content from metadata, validates required attributes, applies duplicate and version rules, and transfers or distributes the asset according to the target API. |
| Collections | Represent curated groups of Showpad content for distribution, organization, or audience-specific delivery. | Salesforce, Microsoft Dynamics 365, Microsoft Teams, reporting stores | Martini retrieves collection membership and related metadata, maps the grouping to target structures or links, and handles missing or changed members explicitly. |
| Tags | Classify and filter Content for product, region, audience, campaign, or governance workflows. | CRM platforms, collaboration tools, databases, reporting exports | Martini converts tags into target labels or filtering attributes, applies business rules, and tolerates new optional values while enforcing required classifications. |
| Portals | Represent branded or audience-specific Showpad content experiences and their selected content context. | CRM platforms, collaboration channels, governance and reporting systems | Martini retrieves Portal information where supported, maps identifiers and audience metadata, and avoids assuming that every Portal change produces an event. |
| Content metadata | Carry descriptive and classification attributes such as title, owner, category, region, expiration, and custom fields. | Salesforce, Microsoft Dynamics 365, databases, CSV or Excel exports | Martini validates and transforms metadata independently from binary files, preserves source identifiers, and routes incomplete or invalid metadata for review. |
Authentication and security considerations
OAuth 2.0 and tenant authorization
Showpad API access uses OAuth 2.0. Confirm the required grant, scopes, redirect or authorization details, token lifetime, tenant endpoint, and administrator approval requirements for the selected Showpad configuration.
Secrets and access control
- Store client credentials, access tokens, refresh material, and tenant configuration in environment-specific Martini secrets.
- Grant only the permissions required by the workflows.
- Do not log bearer tokens, authorization responses, or sensitive content URLs.
- Use separate credentials for development, test, and production environments.
Operational considerations for Showpad integrations
Reliability and throughput
- Assume list endpoints are paginated unless the endpoint documentation states otherwise.
- Confirm Showpad rate limits and apply bounded backoff for HTTP 429 and transient server failures.
- Use stable Showpad identifiers, source IDs, checksums, or canonical URLs for idempotency and duplicate prevention.
- Distinguish Content metadata from binary assets and verify file size, version, rendition, and temporary URL behavior.
Change management
- Define how archived, deleted, and deactivated Users or Content are represented before implementing synchronization.
- Pin or document the API version and tolerate new optional fields while validating required fields.
- Test multi-page reads while records change, callback replay, token expiry, and downstream partial failures.
- Monitor workflow logs and route unrecoverable records to an operational review process.
Why use Martini instead of scripts or point-to-point integrations?
Orchestration beyond a script
Martini provides a maintainable workflow layer for Showpad authentication, pagination, scheduling, callback handling, transformations, business rules, downstream writes, and operational recovery. This avoids duplicating token handling and synchronization logic across point-to-point scripts.
Reusable integration assets
Teams can expose controlled APIs, reuse workflow logic, separate environment configuration from implementation, and apply consistent error handling across Showpad and other enterprise systems. Martini can also combine Showpad REST calls with databases, files, and application APIs without assuming a native Showpad connector.
- Centralize OAuth 2.0 secrets and endpoint configuration.
- Use checkpointing and idempotent processing for repeatable synchronization.
- Apply consistent validation, retry, logging, and exception routing.
Frequently asked questions
Showpad is primarily integrated through its OAuth 2.0-secured REST APIs. Enterprise workflows can retrieve and synchronize Users, Content, Collections, Tags, Portals, and content metadata, while selected event or callback capabilities may support near-real-time processing. Scheduled polling is the fallback when the required event is unavailable.
Yes. Martini can consume Showpad REST APIs, manage OAuth 2.0 authentication, transform Showpad JSON and content metadata, expose controlled REST APIs, receive confirmed webhook-style callbacks, and orchestrate scheduled synchronization workflows.
No. A dedicated Showpad connector is not required. Martini can integrate using Showpad’s confirmed native mechanisms, primarily its REST APIs and OAuth 2.0 authentication, with callback, file, and scheduled polling patterns used where applicable.
Lonti does not charge an additional per-connector or per-vendor fee to integrate Showpad. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Showpad, infrastructure providers, or other third-party systems based on subscription, usage, and deployment model.
Use Showpad’s documented REST APIs with OAuth 2.0 as the primary method. Treat webhook-style callbacks as partial until the required event, payload, security, and retry behavior are confirmed. Do not assume that GraphQL, SOAP, a general bulk API, or direct database access is available.
Showpad may support event or notification-oriented callbacks for selected product and integration scenarios, but broad coverage across all objects and events was not confirmed. Verify the required event for the tenant and API version; use scheduled REST polling when it is unavailable.
Martini can run scheduled workflows that retrieve paginated Showpad resources, apply documented filters or modification fields, and store a checkpoint after successful processing. Stable Showpad identifiers, explicit deletion or deactivation rules, and idempotent writes help prevent duplicates and missed changes.
Yes. Martini can expose a REST API that authenticates and validates incoming requests, calls Showpad’s REST API, applies authorization and business rules, and returns a controlled response without exposing Showpad credentials or unrestricted tenant access.
Related Martini documentation
APIs
Workflows
Connect Showpad with Martini
Use Martini to build secure, maintainable Showpad integrations around REST APIs, OAuth 2.0, scheduled synchronization, content workflows, and confirmed callback events.