Send meeting invitations participants via email after creating a meeting.

Once you create a Adobe Connect meeting and add participants and presenters, you may want to send invitations by e-mail. To send a meeting invitation, you need information about the meeting, including the meeting name, the host’s name and e-mail address, the meeting room URL, the date and time of the meeting, and the participant’s (or presenter’s) name and e-mail address.

You can construct an e-mail message using any technique that works with your user interface. Extract specific information about the meeting using the following steps.

Send an e-mail to meeting participants

  1. Call sco-info with the meeting sco-id:

     https://example.com/api/xml?action=sco-info&sco-id=2006334033
  2. Parse the response for the meeting name, date, or other values:

     <sco account-id="624520" disabled="" display-seq="0"  
             folder-id="2006258750" icon="meeting" lang="en" max-retries=""  
             sco-id="2007063163" source-sco-id="-1625529" type="meeting" 
             version="0"> 
         <date-begin>2006-08-15T09:00:00.000-07:00</date-begin>  
         <date-created>2006-07-27T15:30:43.220-07:00</date-created>  
         <date-end>2006-08-15T18:00:00.000-07:00</date-end>  
         <date-modified>2006-07-27T15:30:43.220-07:00</date-modified>  
         <name>August All Hands Meeting</name>  
         <url-path>/august/</url-path>  
     </sco>
  3. Construct the URL to the meeting room (see Create meeting room URLs).

  4. Call permissions-info to get the principal-id values of the presenters or participants, filtering on permission-id:

     https://example.com/api/xml?action=permissions-info 
             &acl-id=2007018414&filter-permission-id=mini-host
    • For a list of presenters, use permission-id=mini-host.

    • For participants, use permission-id=view.

  5. Parse the response for the principal-id values you want:

     <principal principal-id="2006282569" is-primary="false" type="user"  
             has-children="false" permission-id="view"> 
     <name>jazz doe</name>  
     <login>jazzdoe@example.com</login>  
     </principal>
  6. Call principal-info with the principal-id:

     https://example.com/api/xml?action=principal-info 
             &principal-id=2006282569
  7. Extract the name and email values from the response:

     <principal account-id="624520" disabled="" has-children="false"  
             is-hidden="false" is-primary="false" principal-id="2006282569" 
             type="user"> 
         <ext-login>jazzdoe@example.com</ext-login>  
         <login>jazzdoe@example.com</login>  
         <name>jazz doe</name>  
         <email>jazzdoe@newcompany.com</email>  
         <first-name>jazz</first-name>  
         <last-name>doe</last-name>  
         <x-2006293620>E3612</x-2006293620>  
         <x-2007017651>San Francisco</x-2007017651>  
     </principal>
  8. Call permissions-info again, filtering on a permission-id of host:

     https://example.com/api/xml?action=permissions-info&acl-id=2007018414 
         &filter-permission-id=host
  9. Parse the response for the principal-id:

     <principal principal-id="2006282569" is-primary="false" type="user"  
             has-children="false" permission-id="host"> 
         <name>jazz doe</name>  
         <login>jazzdoe@example.com</login>  
     </principal>
  10. Call principal-info, using the principal-id:

     https://example.com/api/xml?action=principal-info 
             &principal-id=2006258745
  11. Parse the principal element of the response for the name and login (or name and email):

     <principal account-id="624520" disabled="" has-children="false"  
             is-hidden="false" is-primary="false" principal-id="2006282569" 
             type="user"> 
         <ext-login>jazzdoe@example.com</ext-login>  
         <login>jazzdoe@example.com</login>  
         <name>jazz doe</name>  
         <email>jazzdoe@newcompany.com</email>  
         <first-name>jazz</first-name>  
         <last-name>doe</last-name>  
         <x-2006293620>E3612</x-2006293620>  
         <x-2007017651>San Francisco</x-2007017651>  
     </principal>

    These are for the sender of the e-mail, who is the meeting host.

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy