The API Guys

We Integrate Systems

Merge Infusionsoft data into Google Doc or PDF

You can merge data from Infusionsoft into a Google Doc — or PDF — with no code at all. This recipe requires an HTTP Post in an Infusionsoft campaign, a Google Form, a Google Spreadsheet, a Google Doc, and the autoCrat add-on for Google Apps.

1. Prepare the Google Doc merge template. Insert tags formatted as a field name inside double carrots, e.g. “Dear <<firstname>>:”. Use a single word for your field name, but it can be whatever you want. (Click here to see an example.)
2. Set up a Google Form with “questions” for all the data you want to merge. In the form settings under the gear icon, deselect any sign in restrictions (so you can submit data via HTTP Post). (Click here to see an example.)
3. On the Google Form under Responses, click the “more” dots and choose “Select response destination” to set a Google Spreadsheet to hold the data.


4. In the Google Spreadsheet, install the add-on autoCrat.
googlemerge_autcratinstall
5. In autoCrat, create a new job to merge the data from the spreadsheet into the Google Doc. In step 9, be sure to select “Yes” for the option “Run on form trigger”. (If you want to create a PDF instead of a Google Doc, select the correct type in step 4.)

(Here comes the most technical part. In order to create the HTTP Post, you need the form’s POST URL and you need the html names of the fields you want to fill out, which is different than the names you gave them. I recommend copying this information to a text file for reference as you will need to paste it into Infusionsoft.)

6. View the Google Form you created (as if you are going to fill it out) in Chrome.
7. Hover over the blank space on the form just above the title and right click on the from and choose Inspect to open the page source code. A few lines up you should see this: form action=" followed by a URL. Copy the URL to a text file.
8. Hover over the first field you will want to fill out and right click to Inspect again. In the source code scroll down a few lines until you see something that looks like this: input type="hidden" name="entry.1462991265" Copy the name (in this case entry.1462991265) to the text file and note what it identifies.
9. Repeat step 8 for each field. Keep track of which entry name belongs to which information.

Ok, hard part done. Now you should have a text file with a URL and a list of html field names and what they stand for.

10. In a campaign in Infusionsoft (at the point where you want the document to be created), create an HTTP Post.
11. Copy the URL from your form into the POST URL field in the HTTP Post.
12. Add a name/value pair with the name “submit” and the value “Submit”.
13. Add name/value pairs for each of the data fields you want to send to the Google Doc. The name will be the entry name you copied in step 8. The value will be the Infusionsoft merge field, e.g. ~Contact.FirstName~.
14. Set your HTTP Post to Ready and publish the campaign.
Screenshot 2016-08-29 17.01.03

That’s it! When the HTTP Post fires, it will send the data from the values into the form fields you designated as names. That data will be saved as a form entry and will be sent to the spreadsheet. AutoCrat will merge the data from the speadsheet into the Google doc and, if you selected it, create a PDF on your Google Drive.

How to send billing reminders for upcoming subscription payments

The problem: You want to send customers an email that their subscription payment is coming up.
The usual solution: Set up a billing reminder loop sequence
A loop sequence runs repeatedly when triggered from a tag that is removed at the beginning of the sequence and added again at the end. With delays set correctly, a looping sequence will run indefinitely on the prescribed time frame.
1. Set up a campaign that triggers when a tag such as “Trigger Next Billing Cycle” is added.
2. Add five elements to the campaign.
a) Remove tag “Trigger Next Billing Cycle”
b) A delay of the subscription payment interval minus the number of days in advance you want to notify the customer that payment will occur. (For example, if the subscription is paid every 30 days and you want to notify them two days in advance, set the delay for 28 days.)
c) The email to be sent
d) A delay of the number of days in advance you are notifying the client
e) Add tag “Trigger Next Billing Cycle”
3. Make sure the product purchase adds the “Trigger Next Billing Cycle” tag.
Shortcomings of the usual solution:
1. The notification date approximates the billing date, but may not be precise.
2. You can’t put the date of the actual billing in the email.
3. If the date of the subscription billing is changed manually, the contact’s billing cycle campaign must be manually adjusted as well.
4. The process runs indefinitely, so if the subscription is cancelled or limited in number (a payment plan), the notification campaign must be turned off manually or via some other process.
TAG Solution: Store the “Next Billing Date” in a field on the contact record.
When the Next Billing Date is stored in a field on the contact record, you can use a field timer rather than a delay timer to send out the notification email. (Note: The field you use must be a DATE type field. It can be a custom field you create or an existing field such as Anniversary. DATE/TIME fields will NOT work.)
1. Set up a campaign that triggers when a tag such as “Trigger Next Billing Cycle” is added.
2. Add elements to the campaign.
Screenshot 2016-01-18 12.17.47
a) Remove tag “Trigger Next Billing Cycle”
a) An HTTP Post for AnyDate to write the next billing date from the subscription to the Next Billing Date field
HTTPPost_AdvanceBillingNotices
b) A field timer set to run the appropriate number of days before the Next Billing Date
c) The email to be sent
d) A field timer set to run the day after the Next Billing Date
e) Apply tag “Trigger Next Billing Cycle”
3. Make sure the product purchase adds the “Trigger Next Billing Cycle” tag.
This campaign uses the actual billing date on the subscription to trigger the notifications. Because the Next Billing Date is stored in a field on the contact record, you may choose to merge that date into the email. Additional PDev plugins to ActivateSubscription, DeactivateSubscription, and UpdateSubscriptionBillingDate plugins to handle changes in subscriptions and stop, restart, or change the billing notices along with the subscription dates via notes applied or other triggers.

NOTE: If customers may have more than one subscription, multiple campaigns and Advanced Merge Notation will be needed to ensure selection of the correct Next Bill Date from the correct subscription.

Infusionsoft API Mastermind – Appointment Bliss

Infusionsoft API Mastermind – Appointment Bliss

This Week’s Mastermind Project: Appointment Bliss
This week, we will show you how we integrated My Day (Infusionsoft Calendar), Campaign Builder, Google Calendar, Time Trade, Time Fusion and TelAPI to:

1. Enter an appointment once in Infusionsoft and never touch it again
2. Do a two-way sync between Time Trade and My Day (Infusionsoft Calendar)
3. Send reminder emails from campaign builder using exposed appointment info
4. Send automated text reminders for $1 a month and a penny per text
5. Have your clients schedule, reschedule and cancel online

 

Infusionsoft API Mastermind – Integration of Google, Teamwork PM, Harvest Quickbooks and Infusionsoft

Attend the Infusionsoft Mastermind at noon on Thursdays. Then attend our Infusionsoft API Mastermind at 4:30 EDT to see what Infusionsoft-on-steroids looks like!Each week, I present one showcase project that will:

  • spark your imagination,
  • let you see how to overcome Infusionsoft limitations,
  • automate in ways you never thought possible, and
  • leave your competition wondering what the heck just happened!

** Make your projects glide effortlessly, from start to finish, without lifting a finger **

This week, you will see how we integrated Google Mail, Google Contacts, Infusionsoft Opportunities, Teamwork Project Management and Harvest Time Tracking.

No code! Just the big picture concept.

Even if you don’t manage projects, I promise I will open your eyes to more possibilities than you ever dreamed Infusionsoft had.

Download the handout

Webinar Archive: Redirecting and Customizing Based on Actions of Contact

Redirecting and Customizing Based on Actions of Contact

This webinar shows three different ways we can customize the Infusionsoftcontact’s experience, using some simple code and the Infusionsoft API, by redirecting and or customizing based on their actions.

Actions which you might use to base customizations on:

  • Which product did they purchase?
  • How many times have they purchased previously?
  • Do they want subscription or one-time purchase?
  • How did they answer a survey or question on a web form?
  • Where did they come from?
  • What is the lead source?
  • Were they a referral?

Pages or forms you might want to customize:

  • Landing pages
  • Pre-order forms
  • Pre-populated shopping cart items
  • Order forms
  • Thank you pages

Two ways from most basic to most sophisticated

  • Create different pages/web forms/order forms, with different content for each scenario, and use php redirect to send them to the correct one using either IF statements or SWITCH
  • Create  a single destination page and change up the content based on the scenario – you can get much more creative with this one

Download the handout | Take the survey 

©2023 The API Guys