The hottest Integration Substack posts right now

Salesforce has a high P/E ratio, making Power Platform a potential competitor.
Power Platform offers a more user-friendly onboarding experience compared to Salesforce.
Microsoft's existing integrations with Windows and other apps give Power Platform an edge over Salesforce.

The post discusses the concepts of complexity and modularity in tech teams, clarifying how they are often viewed subjectively by architects and engineers.
Vlad Khononov talks about Integration Strength and Coupling Distance as objective measures to identify high coupling within a system.
Readers are encouraged to subscribe to Crafting Tech Teams for more insights and a 7-day free trial of post archives.

Pine now uses a standardized OAuth process for creating public integrations. This makes it easier for developers to connect their applications.
The integration process involves creating an app, redirecting users to Pine's authorization URL, and then exchanging an authorization code for an access token.
There will be one more update about integrations soon, after which development will focus on improving the core application and sharing new research ideas.

Pine now has new editor features like dividers, bullet lists, and various text formatting options, making it easier to organize and style content.
Users can soon programmatically interact with Pine and add custom features, thanks to upcoming API and extension support.
There is still more work to be done on the editor, including creating a preview block and addressing additional tasks.

The Sort API helps automate and manage workflows in Postgres and Snowflake, making it easier for teams to work with their databases.
With Change Requests, users can track, review, and execute changes to their data, which enhances collaboration and transparency.
The API offers powerful querying capabilities, allowing users to define and run their own queries for better data retrieval in their workflows.

Get a weekly roundup of the best Substack posts, by hacker news affinity:

CIAM helps keep user access secure and reduces the stress on teams by managing the entire user lifecycle, from registration to access control.
A major challenge for CIAM is staying compliant with global data privacy laws while ensuring a smooth user experience, especially for business-to-consumer products.
The future of CIAM is promising, especially with improvements in security measures and the need for integration with various technologies for better user identity management.

Build small, just-in-time API prototypes to validate one assumption at a time and get real consumer feedback before you implement the full API.
Use OpenAPI and mock-server tools to quickly turn specs into working prototypes you can share and iterate on as the spec changes.
Prototyping reduces the risk of building unusable APIs, but adoption is limited by delivery pressure and the current lack of unified, low-cost tooling, so teams must weigh the upfront cost against long-term value.

MCP is a standardized way to expose capabilities using JSON-RPC, so it talks about operations (not resources) and is easier to discover and consume than vague REST APIs.
You can call MCP tools from workflows by making JSON-RPC requests, initializing a session to get the mcp-session-id, and mapping each tool's inputSchema to workflow inputs; outputs may be structured or unstructured and might need parsing.
Putting MCP tools into workflows gives predictable, traceable, and more secure execution with easier debugging and reliability, though adapting unstructured tool outputs to procedural steps has some implementation cost.

Make workflows callable as API operations so they can be triggered remotely by webhooks or other services instead of relying on slow, wasteful polling.
Open standards like Arazzo (convertible to OpenAPI) let you describe and chain workflow steps as API operations, but the tooling is new and requires learning and setup.
You can either use built-in webhook support or ready-made workflow tools, or fully convert workflows to OpenAPI; each choice has tradeoffs in complexity, maintenance, and required technical skill or hiring.