Infusionsoft is integrated with ppSD2 through e-mail piping, allowing you to send formatted emails from Infusion to ppSD2 and manage accounts in ppSD2.

Setup

From your website control panel

Create a custom inbox specifically for e-mails generated by infusion from your website's control panel. For example, "infusion_pipe@yoursite.com".

If you are using cPanel:

• "Forwarders" > "Add Forwarder" > "Pipe to a Program"
• /full/server/path/to/ppSD2/modules/infusion_pipe.php

For all other users, create a cron job which uses the following command from your website control panel:

*/2 * * * * php /full/server/path/to/ppSD2/modules/infusion.php

Setup: From your ppSD2 admin control panel

• "Settings > Modules"
• Activate the "Infusion" module.
• Input your mail server settings.

E-Mail Format

Note: all emails need to be sent in plain text format!

Required on all emails:

E-Mail: ~Contact.Email~
Action: Activate or Pause
Key: Your_security_key_here

Optional Fields:

Username: Account_username_here
Password: Account_password_here
Secure Areas: secure_area_name_1,secure_area_name_2,etc. OR all
Digital Products: digital_product_name_1,digital_product_name_2,etc. OR all
Newsletters: newsletter_name_1,newsletter_name_2,etc. OR all
Expires: YYYY-MM-DD HH:MM:SS OR Lifetime OR "Expiration Timeframe (see section below)"
custom_field_name_here: custom_field_value_here

Expiration Timeframes

If you wish for a user’s account to expire "x" hours, days, months, or years in the future, create a combination of a digit, a dash, and either the letter "h", "d", "m", or "y". Examples:

• 1-h: user expires in 1 hour
• 5-d: user expires in 5 days
• 3-m: user expires in 3 months
• 2-y: user expires in 2 years

Things to Remember

• If a username is not included, the user's e-mail address will be used as his/her username
• If not e-mail address is included, a random username will be generated for the user.
• If a password is not included, a random one will be generated
• Secure areas, newsletters, and digital products should be listed with their exact names (cAsE SenSiTiVe) separated by commas
• If the "Action: " line is not included, it will update or create the user's account
• If the "Action: pause" line is included, it will pause the account in question
• The key line must match the custom key you set up within the "Modules" editor of the admin control panel
• If the key is wrong on the e-mail, the user's account will NOT be created, updated, or paused and the e-mail will be deleted from the server.
• Everything within the e-mail sent my infusion is cAsE SenSiTivE! "e-mail" is not the same as "E-Mail", "username" is not the same as "Username", etc.

Sample Infusion-generated E-Mail 1

E-Mail: ~Contact.Email~
Key: your_custom_security_key_here
Username: johndoe
Password: mypassword
Secure Areas: all
Digital Products: May 2008 Issue,June 2008 Issue
Newsletters: all
Expires: 2009-01-01 12:00:00
first_name: ~Contact.FirstName~
last_name: ~Contact.LastName~
Action: Activate

• This example presumes that you have added three custom fields through your ppSD2 control panel: first_name, last_name, and city
• In this example, the user will have access to all secure areas, all newsletters, and 2 digital products: "May 2008 Issue" and "June 2008 Issue"
• In this example, the user's account will expire on January 1st, 2009 at noon

Sample Infusion-generated E-Mail 2

E-Mail: johndoe@johndoe.com
Key: ASCAD2008
Secure Areas: all
Action: Activate

• In this example, the user will have access to all secure areas, no newsletters, and no digital products
• In this example, a random password will be generated for the user and the account username will be set to johndoe@johndoe.com

Sample Infusion-generated E-Mail 3

E-Mail: johndoe@johndoe.com
Key: WRONG_KEY
Secure Areas: all
Digital Products: all
Newsletters: all
Action: Activate

In this example, the e-mail will be ignored and deleted because the "Key: " is incorrect.

Removing Access

To remove access to a secure area, digital product, or newsletter, use the following format. Note that the username must exist in the database for these changes to work.

Username: some_user
Key: YOUR_KEY
Remove Area: Area Name 1
Remove Area: Area Name 2
Remove Newsletter: Newsletter Name 1
Remove Newsletter: Newsletter Name 2
Remove Product: Digital Product Name 1
Remove Product: Digital Product Name 2
Action: Pause

Last updated on 7 July 2011 1:35am