Versions Compared

Version Old Version 3 New Version 4
Changes made by

Stephen Irecki

Stephen Irecki

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

#

Step

Screenshot

Instructions

1

Login:

image-20250211-113949.pngImage Modified

2

Select your

...

Tenant:

image-20250211-114526.pngImage Modified

3

Create an Integration:

image-20250211-115215.pngImage Modified

4

Name your Integration:

image-20250211-114929.pngImage Modified

5

Create an Action:

image-20250211-115330.pngImage Modified

6

Create a new empty Action:

image-20250211-120822.pngImage Modified

7

Name the Action:

image-20250211-121703.pngImage Modified

8

Input a URL and request parameter, and click create:

image-20250211-122316.pngImage Modified

9

Receive success message:

image-20250211-122432.pngImage Modified

10

Select id, title, excerpt and description and click import:

image-20250211-123120.pngImage Modified

11

Success message:

image-20250211-123148.pngImage Modified

12

Click save and then test:

image-20250211-123344.pngImage Modified

Panel
panelIconId1f973
panelIcon:partying_face:
panelIconText🥳
bgColor#DEEBFF

Congratulations on successfully creating your first emite IPaaS Integration! You have configured emite IPaaS to connect to Wikipedia’s API and retrieved information about the 10 top pages relating to your search term.

...

Next Steps:

Panel
panelIconIdatlassian-yellow_star
panelIcon:yellow_star:
panelIconText:yellow_star:
bgColor#DEEBFF

What to do next?

  • You can adjust your search term, back in the Request Parameters section, then re-save and re-test your Action to see what other Wikipedia data you can ingest into IPaaS.

  • You can

...

  • try building integrations to some other Wikipedia API’s

...

  • : https://www.mediawiki.org/wiki/API:REST_API

  • You can apply try applying various rules and transformations to the ingested data. See xyz

  • You can save the retrieved data in a connected data store (Elasticsearch, opensearch) for emite to then visualize

  • You can publish a schedule to always keep the data up-to-date and retrieve new records. See xyz

  • You can save your data to your integration’s cache, to reduce the number of API calls required for subsequent action executions.