We’ve been quiet because we’re hard at work on…. SwiftCloud 3.0 It’s early yet, so we can’t say much about it, but rest assured we’re plenty committed to automation for small businesses. Note SwiftCloud 2.0 is already in “Legacy Mode”, which means we’ll fix any bugs discovered, but no new features on it are being Read More…

Note our Electronic Signature API has 2 parts: Inbound & Outbound eSign / eDocs: Inbound: Inject variables into a contract or doc to be signed. This can even include a base 64 image (say, for an X-ray image, or driver’s license) eSign / eDocs: Outbound: Notification when a doc is signed, including with the URL Read More…

SwiftCloud’s / SwiftCRM’s Calendar is API driven for both internal and external use. HEADS UP! You’ve stumbled into a very technical post. Most users will never need this. If any of the below seems scary and unfamiliar to you, contact us with your goals and we can help. Below is intended for programmers. NOTE: The Read More…

This allows remote systems to post data into SwiftCloud for purpose usually of lead capture, though it can be used for anything – helpdesk, e-sign contract generation flows, etc. SEE ALSO: Domain Mapping – you can map a domain to SwiftCloud servers, even multiple; most common is subdomains like secure.YourDomain.com TIP: SwiftCloud may be pre-integrated Read More…

Welcome Developers! SwiftCloud can help you save time, earn more, impress your clients or team and more. We also speak your language – if you need something, reach out to us. TL;DR: We have inbound + outbound APIs. Inbound = easy, and low risk for us. Inbound data to fill an e-Sign form / contract Read More…

Here’s an example Json file, which translates variable names, below: Why this is needed: SwiftCloud has a few fields that are required, such as name, email Your remote system, such as some other CRM, will take simple POST data, but the variable field-name is different. Example: We store as “name” (which is “full name / Read More…