Supaglue Developer Platform

repository·main·Indexed 19 days ago

https://github.com/supaglue-labs/supaglue

An open-source developer platform for simplifying and scaling B2B product integrations. Supaglue enables developers to sync data from customer CRMs and sales stacks via Managed Syncs, perform operations through a unified Actions API, and receive real-time updates via webhooks. It includes a management UI for controlling applications, customers, sync configurations, and remote providers like Salesforce and HubSpot.

Tokens
244.1K
Snippets
419
Records
566
Agent score
62%

What's inside Supaglue

  1. Overview of Dynamics 365 Sales Connector

    main

    The Dynamics 365 Sales connector uses the Microsoft Dynamics 365 v9.2 API. It supports OAuth2 authentication, managed syncs, a Unified API, data invalidation, and a Passthrough API. It does not support real-time events.

    Supported Objects

    Common Objects

    These objects support both Full and Incremental sync strategies, as well as soft deletes:

    • Account
    • Contact
    • Lead
    • Opportunity
    • User

    Standard Objects

    When specifying standard entities to sync, use their logical name (e.g., mailbox). Syncs are Full or Incremental, but soft deletes are not supported.

    Custom Objects

    Custom objects must be defined in the Power Apps interface with the default publisher. When specifying a custom entity, omit the publisher prefix and use the singular noun. Example: If the logical name is c80e_customobject, specify customobject as the object name. Syncs are Full or Incremental, but soft deletes are not supported.

  2. Overview of the Marketo provider

    main

    The Marketo provider in Supaglue uses the Marketo REST API and belongs to the marketing_automation category.

    Capabilities:

    • Authentication: Supported via marketo_oauth2.
    • Unified API: Supported.
    • Passthrough API: Supported.
    • Managed Syncs: Not supported.
    • Data Invalidation: Not supported.
    • Real-time Events: Not supported.

    Supported Objects:

    • Common Objects: Forms
    • Standard Objects: N/A
    • Custom Objects: N/A
  3. Overview of Outreach connector capabilities

    main

    The Outreach connector (category: engagement) uses the Outreach v2 API. It supports managed syncs, a unified API, data invalidation, and a passthrough API, but does not support real-time events.

    Supported Objects

    ObjectSoft delete supportedSync strategy
    UsersNo*Full or Incremental
    ContactsNo*Full or Incremental
    SequencesNo*Full or Incremental
    Sequences StatesN/AN/A
    MailboxesNo*Full or Incremental

    *Note: Soft deletes are only supported if the sync strategy is set to Full.

  4. Overview of HubSpot Provider capabilities

    main

    Supaglue uses the HubSpot V3 API to support crm and marketing_automation categories.

    Key Features

    • Authentication: Supported via oauth2.
    • Managed Syncs: Supported with various strategies (Incremental, Full).
    • Unified API: Supported with data invalidation.
    • Passthrough API: Supported.
    • Real-time events: Not supported.

    Supported CRM Common Objects

    Common ObjectHubspot ObjectSoft delete supportedSync strategy
    AccountCompanyYesIncremental
    ContactContactYesIncremental
    OpportunityDealYesIncremental
    UserUserYesIncremental (in-memory)
    NOTE

    To sync associations incrementally between common objects, you must configure Webhooks.

    Supported CRM Standard Objects

    Standard objects like company, contact, deal, line_item, product, ticket, quote, call, communication, email, meeting, note, postal_mail, and task all support Incremental syncs and Soft deletes.

    NOTE

    Supaglue does not sync association changes for standard objects until the relevant object is modified in HubSpot.

  5. Apollo Provider capabilities and limitations

    main

    Apollo is a provider categorized under engagement and enrichment. It supports managed syncs, a unified API, data invalidation, and a passthrough API, but does not support real-time events.

    Supported Engagement Objects

    ObjectSoft delete supportedSync strategy
    UsersYesFull
    AccountsYesFull
    ContactsYesFull
    SequencesYesFull
    Sequence StatesYesFull
    MailboxesYesFull

    API Rate and Volume Limitations

    When using Apollo, be aware of the following hard limits:

    • Maximum 10,000 records per Object type.
    • Maximum 10,000 records per hour.
    • Maximum 50,000 records per day.
  6. Supaglue Privacy Policy and Data Handling

    main

    This policy outlines how Supergrain, Inc. (doing business as Supaglue) handles personal information collected through its digital properties and Service.

    Important Note for Business Customers: This Privacy Policy applies to the personal information collected by Supaglue directly. It does not apply to personal information that Supaglue handles on behalf of its business customers while providing integration services. The use of such data is strictly governed by the specific agreements between Supaglue and those business customers.

  7. Understand the Supaglue platform capabilities

    main

    Supaglue provides a platform for product integrations through four primary mechanisms:

    1. Managed Authentication: Securely handles multiple authentication strategies (OAuth2, API keys, access tokens) and maintains sessions (refresh/access tokens) for various providers.
    2. Unified APIs: Provides a single, consistent API interface for reading and writing data across multiple different providers.
    3. Managed Syncs: Automates the process of reading data from providers and syncing it to destinations like Postgres or analytical warehouses (e.g., BigQuery) using Standard, Custom, or Common Objects.
    4. Passthrough APIs: Allows you to call the underlying provider's native APIs directly for use cases not covered by the Unified APIs.
    5. Notification Webhooks: Sends HTTP requests to your API endpoint to notify you of platform events such as completed syncs, new connections, or errors.
  8. Intercom Provider Overview

    main

    The Intercom provider in Supaglue uses the Intercom V2.9 API and belongs to the ticketing category. It supports OAuth2 authentication, managed syncs, a unified API with data invalidation, and a passthrough API. It does not support real-time events.

    Supported Standard Objects

    ObjectSoft delete supportedSync strategy
    adminYesFull
    articleYesFull
    companyYesFull
    contactNo*Full or Incremental
    conversationNo*Full or Incremental

    *Note: Soft deletes for contact and conversation are only supported if the sync strategy is set to Full.

  9. Common use cases for Supaglue

    main

    Supaglue is commonly used for:

    • Lead scoring: Syncing CRM records into your application to power AI/ML models.
    • CRM enrichment: Creating or updating contacts, accounts, tasks, and metrics within a customer's CRM and sales engagement tools.
    • Workflow automation: Automatically adding prospects to email sequences in sales engagement tools.
  10. Salesforce Provider capabilities and object support

    main

    The Salesforce provider uses the Salesforce Bulk 2.0 API and v57.0 REST API. It supports managed syncs, unified API access, data invalidation, and real-time events (alpha).

    Supported Common Objects

    ObjectSoft delete supportedSync strategy
    CompanyYesFull or Incremental
    ContactYesFull or Incremental
    DealYesFull or Incremental
    UserYesFull or Incremental

    Standard and Custom Objects

    • Standard Objects: Use singular Pascal casing (e.g., Account).
    • Custom Objects: When listing custom objects for sync, omit the __c suffix.
    • Syncing: All objects support Full or Incremental syncs and soft deletes.
  11. Overview of Supaglue integration methods

    main

    Supaglue provides three primary ways to integrate with customer SaaS providers:

    1. Managed Syncs: A managed service that continuously synchronizes data from customer SaaS tools into your application database or data warehouse.
    2. Actions API: A unified access point for performing common read and write operations against third-party providers.
    3. Real-time events: A managed service that triggers webhooks to a specified target whenever records are updated in your customers' SaaS tools.