Standard vs. Custom HubSpot-Salesforce Integration
No se pudo agregar al carrito
Solo puedes tener X títulos en el carrito para realizar el pago.
Add to Cart failed.
Por favor prueba de nuevo más tarde
Error al Agregar a Lista de Deseos.
Por favor prueba de nuevo más tarde
Error al eliminar de la lista de deseos.
Por favor prueba de nuevo más tarde
Error al añadir a tu biblioteca
Por favor intenta de nuevo
Error al seguir el podcast
Intenta nuevamente
Error al dejar de seguir el podcast
Intenta nuevamente
-
Narrado por:
-
De:
Running a Salesforce-HubSpot go-to-market stack is one of the most common tech setups in businesses today. Many businesses manage it using HubSpot's native Salesforce integration. But some businesses instead choose to build their own custom integration. Why would they do that? Should your company consider custom-building your HubSpot-Salesforce integration as well?
We talk with Erick Salvatierra on this exact topic. We discuss topics like:
- When should you use the standard HubSpot-Salesforce integration?
- When would a custom integration be better? We discuss specific factors including: sync frequency requirements, field mapping requirements, number of records to sync, compliance requirements, and more.
- If you decide to build a custom integration, how should you do it?- After the integration is built, how should you do maintenance and error handling?
- When should you use an iPaaS / middleware solution vs. fully custom-coding an integration?
- Why should you bother with integration at all?
If you're running Salesforce and HubSpot at a medium- or large-sized company, this episode will be incredibly valuable for you. So give it a like and a watch, and hit that subscribe button so that you never miss any future episodes of The RevOps Hero Podcast.
Todavía no hay opiniones