Integrating With Force.com Using Webhook Handlers
0 likes683 views
The document discusses the challenges of integrating with third-party services on the Force.com platform, highlighting the inefficiencies of polling and manual processes. It advocates for using webhooks as a more efficient method for real-time integration, allowing for user-defined HTTP callbacks that enhance event-driven interactions. Furthermore, it addresses concerns regarding authentication and encourages developers to utilize available code resources from GitHub.
![Authentication
▪ No common standard – read the docs
▪ Call the service back to confirm details match
▪ Calculate a MAC [if supported] using Crypto](https://image.slidesharecdn.com/draftslidesintegratingwithforce-131212223540-phpapp02/85/Integrating-With-Force-com-Using-Webhook-Handlers-8-320.jpg)
Integrating With Force.com Using Webhook Handlers
- 1. Integrating with Force.com Using webhook handlers James Hill & Luke McFarlane, Trineo Ltd, Developers // Salesforce Solutions @oblongmana // @lukemcf
- 2. Safe harbor Safe harbor statement under the Private Securities Litigation Reform Act of 1995: This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties materialize or if any of the assumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results expressed or implied by the forward-looking statements we make. All statements other than statements of historical fact could be deemed forward-looking, including any projections of product or service availability, subscriber growth, earnings, revenues, or other financial items and any statements regarding strategies or plans of management for future operations, statements of belief, any statements concerning new, planned, or upgraded services or technology developments and customer contracts or use of our services. The risks and uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new functionality for our service, new products and services, our new business model, our past operating losses, possible fluctuations in our operating results and rate of growth, interruptions or delays in our Web hosting, breach of our security measures, the outcome of any litigation, risks associated with completed and any possible mergers and acquisitions, the immature market in which we operate, our relatively limited operating history, our ability to expand, retain, and motivate our employees and manage our growth, new releases of our service and successful customer deployment, our limited history reselling non-salesforce.com products, and utilization and selling to larger enterprise customers. Further information on potential factors that could affect the financial results of salesforce.com, inc. is included in our annual report on Form 10-K for the most recent fiscal year and in our quarterly report on Form 10-Q for the most recent fiscal quarter. These documents and others containing important disclosures are available on the SEC Filings section of the Investor Information section of our Web site. Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make the purchase decisions based upon features that are currently available. Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking statements.
- 3. The Problem rd ▪ Getting info from 3 party services is tedious and not timely ▪ Polling is hands-free, but wasteful, and not timely ▪ Doing it manually is wasteful, untimely, and unreliable
- 4. The Usual Suspects “Anything new yet?” “No” “Anything new yet?” “No” “Anything new yet?” “No” “Anything new yet?” “No” “Anything new yet?” “No” “Anything new yet?” “No” “Anything new yet?” “No” “Anything new yet?” “No” “Anything new yet?” “No” “Anything new yet?” “YES” Manual Process *c lic * lick *c *click* k* *click* Polling
- 5. Webhooks ▪ User-defined HTTP callbacks ▪ “Don’t call us, we’ll call you” ▪ Just the events you’re interested in
- 6. Why? ▪ Real-time integration ▪ Efficiency ▪ Quick prototyping and implementation
- 7. Who? … just to name a few
- 8. Authentication ▪ No common standard – read the docs ▪ Call the service back to confirm details match ▪ Calculate a MAC [if supported] using Crypto
- 10. James Hill Luke McFarlane Developer // Trineo @oblongmana Developer // Trineo @lukemcf Copy our code! Code and cliff-notes available at https://github.com/lukemcfarlane/vcg-demo