February 2024 Summaries

Unified.to has introduced several new features and updates as of February 2024, including the launch of a unified Payment API and a Commerce API to streamline integration across fintech and e-commerce platforms, with pre-built support for services like Stripe, QuickBooks, Xero, and Zoho Books. The company has enhanced its webhooks for better data management and introduced new integrations with platforms such as Deputy, Recruitee, Outreach, and Checkr to provide access to diverse data types, including workforce and hiring data. Unified.to also announced being a finalist at the SXSW Pitch and winning the CIX Top 20 Early Award, highlighting its growing influence in the SaaS industry. Additionally, the company continues to receive positive feedback, maintaining a 5-star review streak on G2, and offers improved monitoring of integration support issues through its platform.

Configuring webhooks in HubSpot to integrate with Unified.to involves several steps, beginning with ensuring a HubSpot developer account and the necessary credentials like client ID, client secret, and developer API key. The process includes setting the redirect URL based on the data region and configuring the target URL for webhooks to direct event notifications to Unified.to servers. The setup requires managing subscriptions and scopes, with certain actions potentially necessitating the creation of a new developer app to avoid disrupting existing applications. Scopes must be appropriately assigned, with read and write permissions categorized as required or optional, and Unified.to automates some scope mappings when configuring permissions. In the HubSpot Development Platform, a webhook configuration file is created, specifying target URLs and subscription details, which is then uploaded to deploy the webhook configuration.

Obtaining an OpenAI API key is essential for accessing OpenAI data and automating workflows, requiring users to create or sign in to an OpenAI account, generate a new secret key on the OpenAI Platform, and store it securely as it cannot be viewed again after creation. This key is used for various purposes, including LLM requests, embeddings, and the Ads API. Users may also need to add billing information if they encounter errors like "insufficient_quota." OpenAI utilizes a Unified API approach, eliminating the need for a separate Ads API key. Addressing the need to manage integrations across multiple vendors, Unified.to offers a real-time integration platform that simplifies this process by providing a single, secure API layer across numerous SaaS tools, thereby reducing the need for custom connectors. This platform features usage-based pricing without additional per-connection or setup fees, aiming to provide predictable integration costs.

Unified.to allows users to interact with both common and original vendor-specific objects in integration data by using a "fields=raw" parameter in requests, which returns the original data object alongside the unified format. When reading data, users can request specific fields through a comma-delimited list to limit the returned data to only those fields of interest. For writing data, users include a "raw" field in the payload that contains the integration-specific fields, enabling the modification or overwriting of existing mapped unified fields. This approach provides flexibility in handling both standardized and vendor-specific data elements within integrations.