Parameters – Required

This plugin does not require any parameters other than the standard contactId and App.  If no additional parameters are passed, the newest (latest) subscription will be deactivated immediately.

This field should contain one of the following:

1. A date or date & time which is structurally valid along common standards, such as “January 1, 2014 1:04 PM” or
   “01/01/2014 01:04:33 PM” or “January 1st, 2014″ or “01/01/2014″ etc
2. The text “today” or “now” which will result in using the current date
3. A custom field that is holding a date or date/time value

Note:

Only the date will be extracted from date/time values. Also, if you include a supported timezone code in your date value, please make sure it is using all capital letters (unless it’s an identifier), and that it appears as the last item in the date field. This will be overridden by any timezone values in the time or timezone parameters, if supplied. If no timezones are designated, assume that all dates are in Eastern Time as is the standard with Infusionsoft.

The action to take with the specified contact for the specified webinar. The supported actions are:
1. attendance: Mark the contact as present or absent
2. register: Register the contact for the specified webinar

The ID of the relevant webinar, found in the URL when you are managing your webinar. Look for “webinar=” and copy the number following it. Not that this is not the same as the Webinar ID that is used to join a webinar.

For ‘attendance’ action only. The tag ID that will be applied to the contact if they failed to attend the webinar.

For ‘attendance’ action only. The tag ID that will be applied to the contact if they attended the webinar.

The “to” address that should be receiving the e-mail, designated by

• a fixed e-mail address
• a comma separated list of e-mail addresses
• any Advanced Merge Field Notation that would yield a valid e-mail address

Note:

The value of the parameter will overwrite the value in the “to” field of the email template that is being sent.

The ID of an existing e-mail template in Infusionsoft. Field values within the template, specifically to, from, cc, and bcc, can be over-written by the to, from, cc, and bcc parameters of this plug-in.

This plugin does not require any parameters other than the standard contactId and App.  If no additional parameters are passed, the newest (latest) subscription will be activated immediately.

This plugin does not require any parameters other than the standard contactId and App.  If no additional parameters are passed, the newest (latest) subscription will be deactivated immediately.

The “Call Name” of the API Goal as specified within Campaign Builder. This should be something unique and should have no spaces in it.

Note:

Note: The “Integration Name” of the API Goal should always be your application name (as used for the appName field)

• The sender/originating phone number (assigned & supplied by TelAPI)

• The message to be delivered to the recipient. There is a 160 plain text character limit and a 70 character limit for messages that contain unicode symbols.

• The sender/originating phone number (assigned & supplied by Twilio)

• The message to be delivered to the recipient. There is a 160 plain text character limit and a 70 character limit for messages that contain non-GSM characters.

• The name of the tag category to be used in association with the specified tag.
• The tag category will be created if it doesn’t already exist.

• The name of the tag to be applied to the current contact record.
• The tag will be created if it doesn’t already exist.

• This is the contact Id for the contact record where fields will be retrieved (if any) and where the result of the counter iteration will be stored

• The custom field that is currently storing, or should be storing, the value of this contact’s total amount spent

• This is the contact Id for the contact record where fields will be retrieved (if any) and where the value for total spent will be saved

These are the fields to combine, allowing for a total of 52. Each variable can hold:

• A literal value like 5, 3, or “text”
• field name such as _MyField or Contact._CustomField1

The format is made up of codes, specified by PHP. (Codes are date sensitive.)
Examples of valid codes are:

• Ymd\TH:i:s // This is Infusionsoft’s date format and MUST be used for any Infusionsoft date or dateTime field
• m-d-Y // returns 09-22-2014
• d-m-Y // returns 22-09-2014
• F jS // returns Thursday, September 22nd
• m jS // returns Sep 22nd
• Ymd // returns 20140922

Note:

• For more information about date time codes and formats, see http://www.w3schools.com/php/func_date_date.asp or http://php.net/manual/en/datetime.formats.php

This is the field where the result of the formatted date will be stored, such as Contact.Anniversary, Contact.Birthday, Contact._MyCustomDate or Contact._webinarPrettyDate. Do not put tildes (~) around the name of the field.

Note:

This parameter is optional if using ‘request’.

• The destination StageID for all opportunities found for the specified contact record
• All opportunities found will be set to this specified destination StageID. Add optional parameters to limit the search to specific opportunities (recommended).

Input one of the following:

• The text you want to put in a field, (e.g “New Client”)
• to set the field to empty
• The name of a merge field, e.g. ~Contact.Phone3~ or ~Opportunity._ProjectTitle~. Any Text Anywhere will copy the value it finds in that field to the field being updated.

The name of the field you would like the text copied into, e.g. Contact._NextProject. Do not use tildes (~) around the field name.

Note:

• If add multiple textToSave/saveTo pairs, you must add a number in brackets that matches for each pair, beginning with 0, e.g. “textToSave[0]” and “saveTo[0]” followed by “textToSave[1]” and “saveTo[1]”.
• To append text, use Prefetch to store the destination field’s contents and add the prefetched data back to the same destination field along with the appended text.

This is field one of two whose value will be the basis for some basic operation.
It can be:

• Any standard or custom contact field
• A number that is a literal constant like 3, 2, 2.1, etc.

This is field two of two whose value will be the basis for some basic operation.
It can be:

• Any standard or custom contact field
• A number that is a literal constant like 3, 2, 2.1, etc.

This is the name of the basic operation to be performed on field1 and field2.
It can be any of the following:

• add
• addition
• subtract
• subtraction
• multiply
• multiplication
• divide
• division

The destination field for the calculation.

One of the following:

1. A custom field that is holding a date, date/time value, or a text representation of a date, such as Contact.Birthday or Contact._MyCustomDate
2. A text string representing a valid date or date and time, such as “January 1, 2014 1:04 PM” or “01/01/2014 01:04:33 PM” or “January 1st, 2014″ or “01/01/2014″ etc.
3. The text “today”, which will result in using the current date, or “now”, which returns current date and time.

Note:

• If you merge in a dateTime field for this value, only the date will be extracted.

This is the field where the result of the field combination will be stored, such as _ResultField or Contact._CustomField1.

This is the field whose value will be modified by the counter action, such as _MyField or Contact._CustomField1. Field name should have no merge-field tilde characters.

The direction with which the counter should iterate. Possible values are:

• up
• down
• add
• subtract
• increment
• decrement
• increase
• decrease

The amount of change of the counter iteration. Generally, this should be some positive numeric value, such as 3, 10, 7.6, etc.

A unique name for the API call goal you want to trigger. You will also use this in the API call goal setup.

The number of seconds you want to delay the call for

This is the field where the result of the timezone lookup will be saved. Fields may be standard (e.g. Contact.Phone) or custom (e.g. Contact._MyCustomField). Do not put tildes (~) around the name of the field.

Note:

This parameter is optional if using ‘request’.

Your Infusionsoft application name

Note:

Your application name can be found in the URL used to access your Infusionsoft account. e.g. http://APPNAME.infusionsoft.com.